Systems and methods for incident recording

ABSTRACT

An incident recorder records original and supplemental incident information using a simplified user interface. A lead incident recorder may request any of several support tasks be accepted by other subsystems configured to Follow. Tactical support tasks may be requested. Communication support tasks may be requested. Collection support tasks may be requested. Collection support tasks may include directives for operation of an incident recorder.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/377,766, which is a continuation of U.S. patent application Ser. No.14/842,140, now U.S. Pat. No. 10,269,384, which is a continuation ofU.S. patent application Ser. No. 12/418,540, now U.S. Pat. No.10,354,689, which claims benefit of priority under U.S.C. § 119(e) ofboth U.S. Provisional Application No. 61/042,751, filed Apr. 6, 2008 andU.S. Provisional Application No. 61/158,732, filed Mar. 9, 2009, all ofthe aforementioned are incorporated herein by reference.

BACKGROUND

An incident refers to human or animal activities and to a period of timewhile these activities take place. Incidents include, for example,formation of agreements, transactions, negotiations, discussions,ceremonies, meetings, medical procedures, sporting events, crimes,attempted crimes, disagreements, assaults, conflicts, discoveries,research, investigations, and surveillance. Incidents may includeconsequences including changes to property such as improvements,repairs, construction, production, manufacture, growth, harvesting,damage, loss, theft, burglary, arson, goods damaged in shipment,conditions of real estate, and/or conditions of agricultural andforestry property. An incident may include damage to property and/orinjury to persons or animals. Damage to property or injury to persons oranimals may be accidental or brought on by the action or failure to actof one or more persons. Incidents include information valuable for riskmanagement, insurance, claims, achievements, sports records, newsreporting, and entertainment.

Information (e.g., data, audio, visual, location, environmental)gathered about an incident may describe the incident. Information mayinclude facts about the activities of the incident, consequences of theincident, time of the incident, location of the incident, and identityof humans, animals, or objects related to the incident. Informationabout an incident may form a report of an incident (also called anincident report). Information about the incident may be gathered before,during, or after an incident.

Information about an incident may aid others to determine the identityof the human or animal that performed the activities of the incident,whether activities were properly performed, property affected, human oranimal injured; identity of witnesses, identity of a victims; respondinglaw enforcement and medical personnel; and anyone contributing to theachievement or loss; extent of the loss or the injury; any change inproperty; change in the value of property; and a change in an object,person, plant, or animal.

Information about an incident may be used to establish responsibilityfor the consequences of an incident. For example, whether or not thefacts of the incident require payment under an insurance policy may bedetermined on the basis of a information about the incident. When aweapon is used in an incident, responsibility for a loss or injury mayin part be based on whether the weapon is used within the guidelines ofa law enforcement agency, guidelines set forth by a manufacturer of theweapon, or policies and reasonable behavior or negligence as determinedby local customs, courts, and educational/training institutions.

A report of an incident in many cases may be used as evidence of factsregarding the incident. Evidence may be needed for proof of performanceunder an agreement, resolution of a failure to perform under anagreement, credit for an achievement, proof of damage, injury, crime, orloss, or for enforcement of customs, rules, regulations, laws, judicialorders, or directives from superiors such as employers, partners,custodians, guardians, relatives, officials, or higher ranking officers.

Validation of the information of an incident report includes verifyingthe accuracy and completeness of the information of an incident.Validation of an incident may establish a foundation (e.g., legalfoundation) and provide corroboration for the facts of an incident.Validation may provide foundation and corroboration sufficient for anincident report and the information therein to be used as evidence in acourt.

Accurate and complete reporting of the facts surrounding an incident hasgreat social, economic, and judicial importance. Incident reporting aspracticed in the prior art has limitations that adversely affectaccuracy and completeness. Increased accuracy and greater completenessof incident reports are needed and are provided by systems and methodsaccording to the present invention.

BRIEF DESCRIPTION OF THE DRAWING

Embodiments of the present invention will be described with reference tothe drawing, wherein like designations denote like elements, and:

FIG. 1 is a functional block diagram of a secondary subsystem of asystem for collecting and managing information about incidents,according to various aspects of the present invention;

FIG. 2 is a pictorial representation of a hypothetical incidentinvolving two law enforcement officers apprehending a suspect while eachofficer is operating a respective primary subsystem of a system forcollecting and managing information about incidents, according tovarious aspects of the present invention;

FIG. 3 is a functional block diagram of an implementation of one of theprimary subsystems, herein referred to as an incident recorder, of FIGS.1 and 2;

FIG. 4 is a data structure diagram describing the contents of memory inan implementation of the handset of FIGS. 3 and 7;

FIG. 5 is a plan view of an implementation of the headset of theincident recorder of FIG. 3;

FIG. 6 is a plan view of an implementation of the personal hub of theincident recorder of FIG. 3;

FIG. 7 is a plan view of an implementation of the handset of theincident recorder of FIG. 3;

FIGS. 8A and 8B are state change diagrams of states of the handset ofFIG. 7 while recording original incident information and controlling thedisplay; and

FIG. 9 is a state change diagram of states of the handset of FIG. 7while reviewing incident information.

FIG. 10 is a functional block diagram of a secondary subsystem of asystem for collecting and managing evidence, according to variousaspects of the present invention;

FIG. 11 is a pictorial representation of a hypothetical incidentinvolving two law enforcement officers apprehending a suspect while eachofficer is operating a respective primary subsystem of a system forcollecting and managing evidence, according to various aspects of thepresent invention;

FIG. 12A is a functional block diagram of an implementation of one ofthe primary subsystems, also herein called an incident recorder, of FIG.11;

FIG. 12B is a functional block diagram of an implementation of anotherprimary subsystem, also herein called an activator, of a system forcollecting and managing evidence, according to various aspects of thepresent invention;

FIG. 12C is a functional block diagram of an implementation of anotherprimary subsystem, also herein called an electronic control device, of asystem for collecting and managing evidence, according to variousaspects of the present invention;

FIG. 13 is a data structure diagram describing the contents of memory inan exemplary implementation of the hand set of FIG. 12A;

FIG. 14 is a diagram of a user interface having controls and a displayin an exemplary implementation of the hand set of FIG. 12A;

FIG. 15 is a state change diagram of states of the user interface ofFIG. 14;

FIG. 16 is a plan view of another hypothetical incident involving threelaw enforcement officers apprehending a suspect while each officeroperates a primary subsystem and the suspect comes in contact with aprimary subsystem of a system for collecting and managing evidence,according to various aspects of the present invention; and

FIG. 17 is a communication sequence diagram for communication, accordingto various aspects of the present invention, between the primarysubsystems of FIG. 16.

DETAILED DESCRIPTION

Disclosed herein is a recorder for use by a human operator at anincident includes a head set and a hand set. The head set mounts to turnwith the operator's head. The head set includes a camera oriented awayfrom the operator, a first microphone oriented away from the operator,and a second microphone for picking up the operator's voice. The handset is generally for hand-held operation. The hand set includes binarycontrols, a pointing control, a display and a circuit. The display showslegends for the binary controls and play back of recorded video from thecamera. The circuit stores a sequence of containers containing therecorded audio and video. During playback, the circuit responds to anoperation of the binary controls to freeze a container of video. Thecircuit then adds further audio, video, or graphics. The graphics may bea form with a location specified by the operator via use of the pointingcontrol.

Also disclosed herein is an incident recorder records still photographs,video, and/or audio in response to a user interface. The user interfaceincludes an event control and a privacy control. The recorder has atleast three operating modes, including two modes of recording and atleast one mode for no recording. In response to the application ofprimary power, the recorder operates in a pre-event recording mode. Inresponse to the user operating the event control, the recorder changesfrom the pre-event recording mode to the event recording mode. Inresponse to the user operating the privacy control, the recorder entersthe privacy mode to turn off recording.

An incident report, as discussed herein, is a report of informationabout an incident. An incident report may include information gathered,recorded, documented, explained, classified, described, and/orsupplemented. An incident report may be formed before, during, or afteran incident.

An incident report in a preferred implementation is intended to beadmissible as evidence in a court. For example, an incident report mayconsist entirely of information stored and communicated in one or moresuitable electronic formats.

According to various aspects of the present invention, an incidentreport may include a combination of information, also referred to asincident information, including audio, photographs, video, forms, text,graphics, scans, and electronic documents (e.g., email, word processing,spreadsheets, graphical models, photographs, equipment configurationdata, equipment operation event logs).

Scans include for example scanned paper documents (e.g., tickets,titles, driver's licenses, vehicle registrations, insurance cards, billsof lading, manifests), scanned bar codes (e.g., on products, badges,driver's licenses, hospital reports, receipts), scanned magnetic stripes(e.g., bank cards, driver's licenses), scanned magnetic media (e.g.tapes, disks), scanned optical media (e.g., CDs, DVDs), and scannedglyphs (e.g., on documents, products, badges, driver's licenses).

Incident information may be recorded (e.g., audio, video) to document anincident at the time of occurrence. Recording incident informationcaptures at least some of the information about the incident. Recordingfurther protects against loss of information, for example, by physicalloss or by faulty human memory.

After the first incident information is recorded (e.g., an originalincident report) and available for review, a derivative incident reportbased on the incident information may be developed. A derivativeincident report (also called a revision) includes the original incidentinformation (i.e., unchanged) plus supplemental information.Supplemental information may be added to the original information toenhance an understanding of the original incident information or theincident. Supplemental information may provide additional description ofthe incident. Supplemental information may be formed through selecting,adding, annotating, supplementing, organizing, classifying, emphasizing,and editing, any of which being referred to herein as revising, originalincident information or additional information gathered after theincident. The result of revising is herein called a revision. A revisionincludes original incident information combined with supplementalinformation.

A primary subsystem, according to various aspects of the presentinvention, captures original information and supplemental information toform a revision. Adding supplemental information to original incidentinformation is important because the originally information may notfully capture what was seen, heard, or sensed by the author-operator orclarify any ambiguities in the originally information.

To improve the accuracy of incident reports and to avoid any loss ofinformation due to lapse of time and diminution of human memory, systemsand methods of the present invention provide the author-operator acapability for capturing original information, reviewing, supplementing,and classifying while at or near the incident and/or near the time theincident occurred.

In other words, systems and methods according to various aspects of thepresent invention may employ structures and operations that facilitategathering, reviewing, supplementing, and/or classifying recordedinformation where the supplemental and/or classification information isgenerally recorded at a time soon after the initial incident recordingis made. Furthermore, a primary subsystem according to various aspectsof the present invention enables revisions to be made at the location ofthe incident prior to leaving the location. Making a revision that isspatially or temporally proximate to the incident provides a morecomplete and accurate incident report. Supplemental information providedby the author-operator may result from an analysis of the originalincident information. The author-operator may describe in supplementalinformation and classifications what was seen, heard, or understood bythe author-operator.

Systems for collecting and managing information about incidents,according to various aspects of the present invention, include primaryand secondary subsystems. Primary subsystems are generally used at thetime and place of the incident. Secondary subsystems generally are notused at the time and place of the incident. Primary and secondarysubsystems cooperate to collect and manage information.

A primary subsystem, according to various aspects of the presentinvention, may capture (e.g., record) original incident information thatforms the basis for an incident report. A person that operates a primarysubsystem may be referred to as a user, an author, an author-operator,or simply an operator. A primary subsystem may facilitate any of thefollowing actions performed by the author-operator in any suitableorder: capturing original incident information, timely reviewingoriginal incident information, timely gathering supplementalinformation, timely classifying incident information whether original orsupplemental, and timely preparing one or more revisions.

A secondary subsystem may include any computer system (e.g., personalcomputer, server, network of servers) that receives data from one ormore primary subsystems and stores, manipulates, or reports the data,for example, as evidence. A secondary subsystem may receive data as anincident report. A secondary subsystem may store, select, decompose,classify, sort, combine, compare, analyze, adjust, organize, display inaccordance a classification of the information, and/or control access toincident reports. A secondary subsystem may comprise a hierarchy ofcomponents.

A secondary subsystem may include an evidence manager. A user of anevidence manager may obtain summaries of numerous incident reports usingdatabase query and reporting technologies and may view the results on aworkstation. Submission of an incident report to a secondary subsystemmay occur according to a predefined workflow. Any conventional workflowmanagement technologies (hardware, software) may be used to receive,complete, validate, and authorize use of the incident report. Thesefunctions may be accomplished by different individuals along a workflow.Incident reports of the same incident, but taken from differentperspectives (e.g., different primary subsystems), may be managed inconverging workflows that produce a combined incident report as a newversion.

An incident information, in whole or in part, may be presented to a useron a primary subsystem that includes a display or on a workstation of asecondary subsystem.

While reviewing incident information, whether original or supplemental,an author-operator may record supplemental information or classifypreviously recorded information (e.g., original, revisions). An operatorof a primary subsystem may review, using the primary subsystem, originalinformation or supplemental information to classify any portion of theinformation as belonging to a category.

A category is a descriptor or label that identifies a common aspectamong members assigned to the category. Associating a member to acategory (or a category to a member) is herein referred to asclassifying where a member is a quantity of information recorded or tobe recorded. A member may be identified by selecting any one or moreportions of an incident report. Selection and classification may beaccording to operator input and/or performed according to predefinedselection and classification criteria. Categories may be alternative(e.g., each from a suitable list) or hierarchical (e.g., subcategories)for further classifying incident information. Generally categories arepredefined so that one or more categories or groups of categories may besuggested to the operator for classification. Predefined categoriesdescribe information expected to be part of an incident report orrevision. In addition, categories may be user defined using any userinterface technology discussed herein. User defined categories mayclassify unusual or unexpected information. A category may beimplemented by a storage and/or transmission technology (e.g.,classified information is encrypted or distributed according to a key orplan linked to one or more categories).

Categories for use with law enforcement incident reports may denote anincident type (e.g., traffic stop, burglary, patrol); an expectedincident outcome (e.g., warned, ticketed, arrested); an expected pieceof information (e.g., location, recording of reading the suspectrights); one or more expected types of information that facilitatehandling according to various policies (e.g., unintended recording,recording outside of a mission, recording of unethical or illegalbehavior of a co-worker or associate, recording containing informationthat should be kept secret to avoid a risk of political, legal, social,economic, religious, psychological, or physical consequences).

Categories may determine how information is stored, communicated, and/oraccessed on primary and/or secondary subsystems. Classified information,according to one or more categories associated therewith, may beencrypted using particular keys, stored using a particular technology,transmitted only according to particular policies and protocols, and/orsubject to access or display only according to particular policies andprotocols. For example, information classified as personal-confidentialmay include information unrelated to an incident that was inadvertentlyrecorded.

Categories may identify information that reveals victim identity,politically sensitive information, information proprietary to theprimary subsystem operator, witness identity, innocent bystanderidentity, informant identity, behavior (of a co-worker, celebrity,public figure) that may merit discipline, behavior unbecoming anofficial, information protected by trade secret or copyright law,information related to national security. Classification facilitateshandling such information according to suitable policies beginning withthe original recording and revisions.

A category selected for private information may be used to determine thelevel of authority required to receive, locate, identify, access, and/ordisplay the information on a primary or secondary subsystem. Forexample, an operator of a primary subsystem may classify a portion of anincident report as behavior that may merit discipline. Consequently, theexistence and/or review of that portion of the incident report may beblocked to individuals not providing suitable credentials. Necessarycredentials may belong only to a supervisor or a member of adisciplinary committee. Other staff employees may have little access andthe public may have no access to such information.

Categories (or the effects of classification) are preferably integral toan incident report and its revisions. An information manager of asecondary subsystem may process information about incidents according tothe classification by the author-operator and/or classification byanother person who created a revision.

As discussed herein, original and supplemental recording of informationmay be accomplished with any suitable conventional recording technologyor conventional combination of sensing, detecting, formatting,communicating, and recording technologies.

Supplementing occurs when a first presentation of audio or videocontent, herein also referred to as a movie, whether original orpreviously recorded supplemental information, plays for a durationduring which an operator may indicate an instance in time for adding asecond presentation that provides supplemental information or classifiesthe information (e.g., beginning or ending of selected information to beclassified).

The second presentation may be of any duration and may includeinformation from the first presentation (e.g., an excerpt) orsupplemental information from another source. The second presentationmay be limited to a still photograph with no audio (e.g., a frame fromthe video of the first presentation), a short loop of one or a fewmoments (e.g., a scene, one or more frames of video from the firstpresentation). In the second presentation, the operator's supplementedinformation may emphasize or describe an audio occurrence (e.g., agunshot, a few words, a noise) or a visual occurrence (e.g., a glance, afacial expression) of the first presentation.

In a preferred implementation, a record of an incident is stored,reviewed, revised, and communicated in accordance with “Coding of MovingPictures and Audio”, an ISO/IEC standard, known as MPEG-4. Informationin MPEG-4 format is contained in containers, defined by the format.Information recalled from an MPEG-4 containers may be used to composescenes, movies, descriptions, supplemental information, andclassification as discussed herein. Metadata describing a container mayidentify whether or not one or more categories (possibly furtheridentifying which categories) have been associated with the content ofthe container.

Primary subsystems may perform any one or more of the followingfunctions in any suitable combination: detecting for collectinginformation, recording information (e.g., original, supplemental),forming a revision, selecting information for classification,classifying information, communicating among components identified tothe same operator (herein also called a personal primary subsystem),storing the identity of the operator, communicating between a primarysubsystem and a secondary subsystem, storing addresses forcommunication, receiving software and data from a secondary subsystem,and transmitting status, data, an incident report, or a revision to asecondary subsystem.

A primary subsystem may be packaged in several units (e.g., productsindividually sold or handled) (herein called components) that cooperateby wired or wireless links to participate in performing the set offunctions of the primary subsystem. A component may perform somefunctions without communication with other components of the primarysubsystem.

A primary subsystem may include a detector, a recorder, and a userinterface for reviewing and managing incident information (e.g.,preparing supplemental information, selecting, classifying). A detectormay detect any ambient condition: video, audio, ambient information(e.g., temperature, amount of light), or scanned information. A videodetector may include a video camera oriented by the author-operator forrecording whatever is in the field of view of the author-operator.

A primary subsystem may format detected information for recording orcommunicating recorded information. Preferably, detected information,whether original or supplemental, is formatted according to a format ofthe type known as MPEG-4. A classification may apply to the informationof an entire MPEG-4 container or any portion of a container. Containersmay be arranged in hierarchy for applying a classification of a parentcontainer to all its children. A classification for one MPEG-4 containermay apply to all subsequent (e.g., playback) MPEG-4 containers untilreaching an MPEG-4 container having a different classification.

A recorder may store detected or revised information. A recorder maystore information as MPEG-4 containers. An original incident report andrelated revisions may be stored serially or in hierarchy using anyconventional recording and storing technologies.

A user interface may facilitate gathering original and supplementalinformation, forming an incident report, reviewing original andsupplemental information, selecting information for classification,classifying information, and preparing revisions.

A user interface may include a display and controls. A display of ahandset may be implemented using conventional touch screen technologies.A display may provide touch screen legends (e.g., icons) for manualselection by a user. A user interface may be implemented usingconventional interactive-voice-response (IVR) technologies (e.g., theuser interface recites an audio script with prompts (e.g., true/false,multiple-choice) to elicit a response from the user. A user may respondto an IVR script, for example, by speaking into a microphone of the userinterface, selecting a legend on a touch screen display, or operating acontrol.

A user interface may further include controls to start, stop, or togglefunctions of the primary subsystem (e.g., start if stopped, stop ifstarted). User operated controls may be positioned on one or morecomponents of the primary subsystem. A primary subsystem having controlson more than one component (e.g., handset, hub) that perform the samefunction may respond to operation of either or both controls. Operationof a control may result in a presentation of multiple-choice legends onthe display for selection by the user. Functions performed by operationof a control may include start recording, stop recording, togglerecording on/off, toggle display on/off, and mark selection, review, orrevision. The primary subsystem is said to be in a privacy mode (orperforming a privacy function) when it is not recording.

Methods, according to various aspects of the present invention, increasethe likelihood that an incident report is complete, accurate,corroborated, verifiable, accessible, integrated with other sources ofinformation, and reliably stored (e.g., for use as evidence). Thesefunctions and advantages may be obtained by virtue of the variety ofelements of an incident report (e.g., sounds, movies, forms, text,graphics, documents, scans) and the capability of revising a scene basedon any or all of these by the author-operator of the primary subsystem.

Revisions may improve the emphasis or clarity of an incident report.Video images may be cropped, panned, and/or zoomed. Movies may beclipped. Photographs may be cropped and/or scaled. Audio streams may beclipped. Printed information may be amended or partially rewritten forclarity. Supplemental information may be provided by the author-operatorregarding the original recording. All of these revisions may occur atthe primary subsystem by operation of a user interface. The time (e.g.,time of day, date) of making a revision may also be recorded. Theoriginal recordings are preferably retained. The revisions preferablyform a new version of the incident report.

For example, a system for collecting and managing evidence may includeany number of station hubs (e.g., secondary subsystems) coupled by anetwork to any number of shift hubs (e.g., secondary subsystems). Astation hub provides secure operation of a manager of information aboutincidents (e.g., an evidence manager). A network supports data andinter-process communication. Any conventional protocol may be used(e.g., an internet or intranet protocol stack). A shift hub providesdata transfer from a primary subsystem (e.g., incident reports andrevisions), recharging of rechargeable batteries, and/or data transferto the primary subsystem (e.g., software upgrades, information regardingtactical tasks, evidence collection tasks, communication tasks).

For example, a system for collecting and managing information aboutincidents 100 of FIG. 1 includes station hub 110 coupled by network 114to shift hub 120. Station hub 110 hosts evidence manager 112 (e.g., adatabase manager adapted in a conventional manner for managingevidence). Hosting includes a conventional secure computing environment(e.g., physical security, communication security, access controls,encryption, personnel authentication). Network 114 provides securecommunication between any number of station hubs 110 and shift hubs 120.Shift hub 120 includes a processor 122, an ad hoc transceiver 124 forwireless communication with any suitable number of primary subsystemsequipped for wireless data transfer, docks 126 for wired connection toany suitable number of primary subsystems, a device identificationdetector 128, and a person identification detector 129.

Processor 122 via ad hoc transceiver 124 and docks 126 may poll primarysubsystems or components that are within range for maintaining wirelessad hoc communication based on one or more suitable communicationchannels (e.g., conventional IR, radio, or wireless network channels)and using one or more suitable communication protocols (e.g.,conventional IEEE 802). Such a network is “ad hoc” because candidates ofthe network may enter and members of the network may exit (e.g., movedby humans) the zone of communication without advance notice to processor122. Processor 122 detects entry and exit of a primary subsystem andcomponent from the ad hoc network and maintains the ad hoc network withas many members as practical for the capability of processor 122.

A device identification detector detects an identification of acomponent of a primary subsystem or of an entire primary subsystem(e.g., a personal primary subsystem). For example, on check-in to shifthub 120 (e.g., via docking or local ad hoc communication), deviceidentification detector 128 identifies the components or a primarysystems and associates the detected identities to the incident reportstransferred from the components or primary subsystems to shift hub 120.Identification and association provides evidence validation (e.g.,custody, control). On checkout from shift hub 120 (e.g., via undockingor removal from local ad hoc communication), device identificationdetector 128 identifies components to the primary subsystems (e.g., inthe same or another component) so that incident reports are recorded inassociation with that component's identification, again for purposes ofevidence validation.

A person identification detector detects an identity of a personassociated or to be associated with a primary subsystem. For example, oncheck-in of a primary subsystem to shift hub 120, the person that plugscomponents of the primary subsystem into docks 126 may be identified byperson identification detector 129 for association to the incidentreports transferred from the primary subsystem for purposes of evidencevalidation. On checkout of a primary subsystem from shift hub 120 (e.g.,removal from docks 126), the person that removes components of theprimary subsystem may be identified to the primary subsystem so thatincident reports are recorded in association with that person'sidentification, again for purposes of evidence validation.

Docks 126 accept, by plug-in to a wired network, any suitable number ofprimary subsystems or components thereof. Docks may also provide alocation (e.g., a bin) within range of ad hoc transceiver 124 forcommunication between processor 122 via transceiver 124 and any numberof primary subsystems or components thereof placed at the location(e.g., in the bin). The location may be suitable for detecting deviceidentification by device identification detector 128. For example,handsets 132 and 134 may be plugged into docks 126. Headsets 222 and232, personal hubs 224 and 234 may be located in a bin (not shown) forscanning or programming by device identification detector 128.

Docks 126 locate and link for communication components and primarysubsystems for data transfer to secondary subsystem 110 as coordinatedby processor 122 and evidence manager 112. Data transfer may includeoriginal and supplemental information, incident reports, classificationwithin incident reports, and usage logs. If other components of primarysubsystems are nearby but not plugged into docks 126, data transfer mayoccur via ad hoc transceiver 124 as controlled by processor 122 forcommunication with those other components and primary subsystems capableof wireless communication.

A hypothetical incident and application of systems and methods accordingto various aspects of the present invention is illustrated in FIG. 2.FIG. 2 pictorially represents a hypothetical incident involving two lawenforcement officers 206 and 204 apprehending a suspect 202 while eachofficer operates a respective primary subsystem, herein called a systemfor incident recording 208 and 209 (herein also called an incidentrecorder), according to various aspects of the present invention.

Officer 204 operates an electronic control device 210 (e.g., a TASERInternational model M26 or X26 device) that deploys two wire-tetheredelectrodes and hits suspect 202 at contact points 212 and 214. Currentgenerated by the electronic control device flows through the wires,electrodes, and tissue of the suspect to cause involuntary musclecontractions, halting locomotion by the suspect and facilitating arrestof the suspect. Incident recorder 208 worn by officer 204 records amovie (e.g., original audio and video information) during theconfrontation. System for incident recording 209 worn by officer 206also records a movie during the confrontation from a different point ofview.

In this example, systems 208 and 209 are identical. Each system includesa headset 222 (232), personal hub 224 (234), handset 132 (134), andon-duty transceiver 228 (238). Each headset 222 (232) includes a cameraand microphone oriented away from the officer toward the field of viewof the officer's eyes. Soon after suspect 202 is arrested (e.g., handcuffed, shackled, confined), officer 204 (206) may independently reviewthe movie that was recorded and add supplemental information andclassifications to any portions of the movie.

Reviewing is accomplished by watching previously recorded information onthe display of the handset. Adding a quantity of supplementalinformation (e.g., adding a description) is accomplished, among otherthings, by identifying a scene, and adding audio (e.g., talking aboutthe scene into a microphone of the headset or personal hub), addingvideo (e.g., removing the camera from the headset and orienting ittoward anything of interest), or adding graphical information (e.g.,describing in a standardized way where on the body of the suspectcontact points 212 and 214 occurred).

Classifying is accomplished by reviewing previously recorded information(e.g., original, supplemental, revision) selecting recorded information(or designating information to be recorded) and associating one or morecategories (e.g., subject matter) to the selected information. Aclassification may apply to any portion of a movie. Recorded informationmay have one, several, or no classifications.

In an implementation, a system for incident recording 208 of FIG. 3includes handset 132, personal hub 224, and headset 222. Handset 132includes processor 340, memory 341, video monitor 342, controls 343,handset speaker 344, audio in circuit 345, audio out circuit 346,handset mike 347, accelerometer 348, and wired/wireless interface 349.Personal hub 224 includes hub mike 324, hub speaker 326, and controls328. Headset 222 includes head mike 334, oriented mike 335, head speaker336, oriented camera 337, and orientation detector 338.

In another implementation, incident recorder 208 or 209 includes headset500, personal hub 600 and handset 700. Headset 500 includes orientedcamera 510, oriented mike 520, head mike 530, head speaker 540,orientation detector 550, and conductor 560. Personal hub 600 includeshub mike 620, volume 624, hub speaker 626, event switch 630, privacyswitch 640, privacy indicator 642, conductor 560, and conductor 612.Handset 700 includes power switch 720, handset speaker 722, volume 724,handset mike 726, display 730, picture-in-picture 732 portion of display730, legends 740, event switch 750, privacy switch 760, privacyindicator 762, display toggle switch 770, and conductor 612.

The functions and functional cooperation of the components of theincident recorder are discussed below.

A handset, according to various aspects of the present invention,provides a display and provides controls sized and positioned foroperation by a user's fingers or thumbs. A handset operates to recordoriginal incident information. A handset operates to review originalincident information and to record supplemental incident information. Ahandset operates to classify original and supplemental incidentinformation. A handset may receive information from another component ofthe incident recorder (e.g., hub, headset) for recording by the handset.A handset may communicate an incident report to other portions of anincident recorder or to a secondary subsystem.

For example, handset 132 (700) receives from personal hub 224 (600) orheadset 222 (500) signals that convey audio or video information.Handset 132 stores the audio and video information in MPEG-4 format inmemory 341. In another implementation, personal hub 224 (600) is omittedand handset 132 (700) cooperates directly with headset 222 (500) througha wired interface to convey audio and video signals and to record thesignals. In another implementation, headset 222 (500) is omitted andhandset 132 includes a microphone and speaker for use by theauthor-operator of the handset and an oriented microphone (not shown)and oriented camera (not shown) that are oriented by the author-operatorof the handset.

A personal hub, according to various aspects of the present invention,couples one or more of a headset and a handset. A personal hub mayinclude a wired interface or a wireless interface to a headset or aheadset. A personal hub may include controls for operation by a user'sfingers or thumbs. Some controls of a personal hub may perform operatefunctions similar to the controls of a handset. While a personal hub iscoupled to a handset, the controls on either the handset or the personalhub may be used to operate the handset.

For example, personal hub 224 (600) provides a wired interface toheadset 222 (500) and handset 132 (700). An operation of event switch630 or privacy switch 640 operates on handset 700 to perform the samefunctions as an operation of event switch 750 or privacy switch 760.

A primary subsystem may be implemented without a personal hub where, forexample, a user interface of the handset is sufficient for intendedoperations of the primary subsystem.

A headset is adapted to couple to a head of an author-operator. Aheadset, according to various aspects of the present invention, supportsvisual and audio detectors. A headset may have a predeterminedorientation on an author-operator's head. A detector may be orientedwith respect to the headset and thus be oriented with respect to theauthor-operator's head. An oriented detector may include any device fordetecting physical phenomena that is oriented (e.g., positioned) along asame general direction as a sense (e.g., sight, hearing) of theauthor-operator.

A headset may include, as an oriented detector, a microphone fordetecting sound. The microphone may be oriented in a direction ofhearing of the author-operator. A headset may include, as an orienteddetector, a camera for detecting radiant energy in any suitable channelor spectrum in a direction of sight of the author-operator.

A headset may include a source of radiant energy (e.g., laser, light, EMpulse) and a detector for detecting radiant energy from the source thatis reflected towards the headset. A headset may include a laser foridentifying a reference location or for use as a designator fororienting a data source or targeting weapons.

For example, headset 222 (500) is worn on the head of a human operator.Headset 222 (500) includes oriented microphone 335 (520) and orientedcamera 337 (510) for continuously detecting audio and visual (orinfrared) information from the direction facing the operator. Becausehandset 222 (500) is attached to the operator's head, the orientation ofmicrophone 335 (520) and oriented camera 337 (510) retains itsorientation in the direction facing the operator as the operator turnshis or her head to face a different direction. Headset 222 (500) furtherincludes microphone 334 (530) and speaker 336 (540) located proximate tothe mouth and ear respectively of the human operator for receivingdescriptive information from the author-operator and for providing areview of recorded information.

A processor includes any circuitry or subsystem that performs a storedprogram. A processor may include a dedicated digital signal processor, amicrocontroller, a microprocessor, an application specific integratedcircuit, logic circuitry, MEMS device, signal conditioning circuitry,communication circuitry, a computer, a radio, a network appliance,combinations thereof in any quantity suitable for accomplishing one ormore stored programs.

For example, processor 340 includes a digital signal processor fordigitizing audio signals, a microcontroller for supporting video displayand user interface controls, and a microcomputer with an operatingsystem and application software for performing all other functions ofhandset 132 (700). In another implementation, greater signal processingthroughput is supported with additional parallel processing circuits andtechnologies.

A memory includes any semiconductor, magnetic, optical technology, orcombination thereof for storing information. All or a portion of memorymay be on removable media removed from handset 132 (700) fortransferring data out of handset 132 (700) or for introducing data intohandset 132 (700) (e.g., software upgrade, replacement information forany information described with reference to FIG. 4). For example, memory341, stores information as described with reference to FIG. 4 usingnon-removable semiconductor technology. A portion of memory 341 may bemaintained in nonvolatile memory to avoid data loss in the event offailure or removal of battery power to handset 132 (700).

A video monitor provides a display of video information (e.g., a movie).A video monitor may present legends for controls of a user interface. Avideo monitor may present video information as it is being originallyrecorded and recorded information for review. A video monitor maypresent supplemental video information. A video monitor may include aprocessor or circuitry for supporting the display. A video monitor mayemploy any display technology suitable for the environment in whichhandset 132 (700) is used. In an implementation, video monitor 342includes a conventional LCD display that presents video in shades ofgreen for visibility outdoors. In another implementation, video monitor342, or a monitor in addition to video monitor 342, is included inheadset 222 (500) and the correlation of legends on the display withcontrols of the user interface does not require the trained user to viewhis or her hands when operating the controls. In another implementation,video monitor 342 includes a touch-screen display (730) that receivesauthor-operator input via author-operator contact with the display.

A control, according to various aspects of the present invention, is apart of a user interface that provides input to a processor in responseto an action by an author-operator. A control may be operated as aconsequence of any muscle contraction by the operator. A control may beincorporated into clothing worn by the operator (e.g., gloves, sleeves,shoes). A control may provide analog or binary information to aprocessor. A control may comprise a detector of a binary condition or adetector of an analog condition. A control may include a portion of atouch-screen display.

For example, controls 343 include a first plurality of touch-screenlegends 740 (four legends shown) positioned on display 730 of videomonitor 342. Legends may be organized as hierarchical menus. Thetouch-screen legends of controls 343 may be sized and positioned on thedisplay of handset 132 (700) for operation by the operator's thumbs.Operation (e.g., touching, pressing, selecting) of touch-screen legend740 selections the function indicated by the legend. Legends 740 may bedefined and redefined by processor 340 within any suitable operatingcontext, state, or mode of operation, thus many if not all functions ofhandset 132 may be operated via legends 740.

Controls 343 may further include dedicated switches that when operatedinitiate performance of a dedicated function. In one implementation,operation of event switch 750 (630) starts the recording of incidentinformation by handset 132 or 700, operation of privacy switch 760 (640)stops the recording of incident information by handset 700, operation ofdisplay switch 770 toggles the operation of display 730 between anon-state and an off-state. While personal hub 600 is coupled to handset700, an operation of event switch 630 and privacy switch 640 perform thefunction of event switch 750 and privacy switch 760 respectively.

In another implementation, controls 343 include multiple-functionswitches. A function performed by multiple-function switch depends uponthe operating context of handset 132 or 700. While handset 700 operatesto gather original incident information, event switch 750 (630) andprivacy switch 760 (640) operate as described above. While handset 700operates in a review mode in which original information or previouslyrecorded supplemental information is presented on display 730, eventswitch 750 (630) toggles recording to start and stop recording ofsupplemental information by handset 132 or 700; and privacy switch 760(640) initiates presentation by handset 132 or 700 of suggestedcategories as touch-screen legends 740 to facilitate classification.When a touch screen legend is touched by the operator, handset 132 (700)classifies the selected information by associating the category of thelegend to the selected information.

Controls 343 may further include power switch 720 and volume switch 724(624). An operation of power switch 720 toggles power to handset 700 onand off. An operation volume switch 724 (624) increases or decreases theaudio volume provided by handset speaker 722, hub speaker 626, or headspeaker 540.

Head speaker 540 may include conventional headphones or ear buds.

An audio-in circuit provides audio information to a processor in asuitable signal format. Signal conditioning, analog to digitalconversion, sampling, multiplexing, and filtering may be accomplished byan audio-in circuit. For example, audio-in circuit 345 provides toprocessor 340 audio information responsive to analog microphonesincluding handset mike 350 (726), hub mike 324 (620), head mike 334(530), and oriented mike 335 (520). Conversion to MPEG-4 format may beaccomplished by processor 340 or audio-in circuit 345.

An audio-out circuit receives audio information from a processor in asignal format suitable for communication or conversion into sound. Forexample, audio-out circuit 346 in cooperation with processor 340converts audio information from MPEG-4 format to analog format for useby a conventional speaker (e.g., head speaker 336 (540), hub speaker 325(626), handset speaker 334 (732)). In another implementation, audio-incircuit 345, processor 340, and audio-out circuit 346 cooperate toprovide audio output for use with conventional noise cancellationtechnologies implemented at hub speaker 326 (626) or head speaker 336(540). In an implementation, additional microphones are co-located nearspeakers to provide additional signals to audio-in circuit 345 andprocessor 340 for performing noise cancellation. Processor 340 andaudio-in 345 may include noise cancellation processing circuitry orsoftware.

As used herein, a signal conveys information. A signal may be conveyedon a conductor or recognized as a particular value in a processor (e.g.,340) or memory device (e.g., 341). When a functional block is responsiveto information, the circuitry implementing the functional block receivesa signal that conveys the information and demodulates, or otherwise,determines the information for performance of a function of the block.Receiving may be continuous or discontinuous. Performing the functionmay occur whenever sufficient information is received.

Components (e.g., handset 132 (700), personal hub 224 (600), headset 222(500)) of an incident recorder (e.g., 208, 209) may each includerespective device identification functions. A device identificationfunction may be implemented in any conventional manner to identify thecomponent of a primary subsystem to a shift hub as discussed above. Theidentification may be human readable as well as machine-readable. If acomponent includes a user interface, the device identification may beentered, edited, augmented, or verified by the operator.

Hub microphone 324 (620) and hub speaker 326 (626) pick up theoperator's voice and play audio into the operator's ear respectively.Hub microphone 324 (620) provides an analog signal conveying audioinformation to audio-in 345. Hub speaker 326 (626) provides audiblesound in response to a signal received from audio-out 346. Hubmicrophone 324 (620) and hub speaker 326 (626) provide redundantfunctions with head microphone 334 (530) and head speaker 336 (540).

Audio-in 345 receives audio information from hub mike 324, head mike334, oriented mike 335, and handset mike 347. In suitable relativevolumes among these audio sources and at suitable times based on apriority of audio sources, audio-in 345 provides audio information toprocessor 340.

Audio-out 346 receives audio information from processor 340. In suitablerelative volumes among these audio sources and at suitable times basedon a priority of audio sources, audio-out 346 provides audio informationto handset speaker 344 (722), hub speaker 326 (626), and head speaker336 (540).

Head microphone 334 (530) and head speaker 336 (540) pick up theoperator's voice and play audio into the operator's ear respectively.Head microphone 334 (530) provides an analog signal conveying audioinformation to audio-in 345. Head speaker 336 (540) makes audible soundin response to a signal received from audio-out 346. Due to the locationon the operator's head, head microphone 334 (530) and head speaker 336(540) may provide more private audio communication with anauthor-operator than possible with hub microphone 324 (620) and hubspeaker 326 (626) or handset microphone 347 (726) and handset speaker344 (722).

An oriented microphone moves with movement of the author-operator's headto receive sound that approaches the operator's face. An oriented cameramoves with movement of the author-operator's head to capture radiantenergy (e.g., ambient or illumination of visible or IR light) thatapproaches the operator's face. Consequently, as an author-operatorperforms his or her routine, audio and visual information captured forrecording generally corresponds to the audio and visual information thatreaches the author-operator's senses. Oriented mike 335 (520) may have arelatively narrow field of sensitivity projected in front of theauthor-operator suitable for capturing speech intended for theauthor-operator to hear and respond to. Oriented camera 337 (510) mayhave a relatively wide field of sensitivity to correspond more closelywith the field of view of a human author-operator. Oriented microphone335 (520) may be implemented as an omni-directional microphone or stereomicrophone and as such may not be “oriented” in the same manner thatoriented camera 337 is oriented.

Memory 341 includes data stored in any suitable organization and format.In one implementation, contents of memory 341 include data structures400 as described below with reference to FIG. 4. Data may be organizedfor storage in a data structure of any conventional type includingvalue, list, table of records, file, tree, graph, hierarchy of records,or hierarchy of tagged strings consistent with a markup language. Datain any organization and plural organizations may be stored incontainers. The description of memory 341 shown in FIG. 4 is more akinto a functional block description than a data structure or containerdescription. Nonetheless, the data stored in memory 341 and the mannerin which it is accessed by processor 340 specifies the structure ofmemory 341.

A wired and/or wireless interface provides communication between handset132 and shift hub 120. The wired interface enables handset 132 toelectrically couple to dock 126 to communicate information betweenhandset 132 and shift hub 120. A wireless interface enables handset 132to wirelessly communicate with ad hoc transceiver 124 of shift hub 120.In one implementation, handset 700 uses a wired interface to couple bothbattery charging currents and data communication signals to docks 126 ofshift hub 120.

An orientation detector detects an orientation and a change inorientation of an object. An orientation detector may report anorientation or a change in an orientation of an object. An orientationdetector may provide an analog or digital signal consistent with anorientation of an object. An orientation detector may detect anyphysical property (e.g., gravity, inertia, magnetic field, EM waves) orchange in a physical property to detect orientation or a change inorientation. In one implementation, orientation detector 338 (550)includes a three-axis gyroscope that detects the orientation and changesin the orientation of headset 222 (500) and thus the orientation of theoperators head. The orientation of the operator's head may be recordedwith and be correlated to other incident information.

Information provided by an orientation detector may be used for anypurpose suitable for incident recording. Orientation information may beused to index incident information for review and searching. Forexample, handset 132 or 700 may provide a list of locations in originalincident information in which the author-operator oriented headset 500toward himself or herself (e.g., look down, look at feet). Such anorientation may include unintended recording and be suitable forclassification as personal-confidential as discussed above by operationof handset 132 (700) without user input for selection of information oridentification of a category. Similarly, an automatically prepared indexof original or supplemental information formed with respect to headsetorientation may be presented as legends to permit a user to search forlocations in which headset 222 (500) was oriented at a preprogrammed oruser-identified orientation. Orientation for automatic classificationmay be defined relatively (e.g., to the right) or absolutely (e.g., tothe north-west).

Data structures 400 include program code 402, local logs 404, audio hubmike streams 406, audio head mike streams 408, audio oriented mikestreams 410, audio handset mike streams 412, video oriented camerastreams 414, supplemental documents 416, supplemental audio streams 418,supplemental video streams 420, menus 422, classification information424, other data 426, interactive-voice-response streams 428, andorientation information 430.

Program code 402 includes instructions performed by processor 340 toaccomplish any methods and functions ascribed to processor 340 orhandset 132 (700). Program code 402 includes operating systems forprocessor 340 and application software. Application software includessoftware for recording audio and video in MPEG-4 format, software foroperating a user interface for a handset as discussed herein, softwarefor reviewing recorded information, software for determining revisionsin MPEG-4 format, software for classifying incident information, andsoftware for communications.

For improved information gathering and transfer, application softwaremay further include software for noise cancellation, video enhancement(e.g., stabilization, bounce removal, light level compensation),identification of the author-operator of the camera (e.g., duringrecording) and the handset (e.g., during revising), identification ofother components of the incident recorder (e.g., serial numbers, types,manufacturers), interactive voice response, transcription of speech totext, and 3D modeling for graphic presentations including datacollection graphics.

Recorded audio and video may be stored for at least two purposes. Apre-event buffer may retain continuously recorded audio and videoinformation in a circular buffer (e.g., 60 seconds duration) so thatwhen the operator indicates a time to begin recording an event (e.g.,operation of a control 343 or 328), audio and video from before theoperator's indicated time is available, for example, to provideinformation as to why the user decided to begin recording the event(e.g., incident, revision).

Any number of events may be recorded, preferably one event at a time.The end of each event may be indicated by the author-operator byoperation of control 343 or 328. Controls 343 or 328 may include adedicated switch (e.g., event switch 630 or 750) for indicating a startand an end of an event. Menus may permit the user to actuate legends 740to indicate the end of an event.

An incident report may include supplemental information as describedabove. Supplemental information may include portions of logs,interactive voice response streams, data collection forms or overlays, auser provided classification, data collection graphics or overlayswhether or not any or all of this information is included in a revision.In a preferred implementation, a revision includes all relevantinformation including one or more movies, all scene descriptions,portions of logs, interactive voice response streams, classifications,data collection forms or overlays, and data collection graphics oroverlays.

Storage of recorded audio or video in a “buffer” as stated herein doesnot designate a format for storage. A buffer as used herein may hold anyaudio or video stream in any format (e.g., MPEG-4 format). A pre-eventor event stored in a buffer does not designate a contiguous region ofmemory. Streams that are part of a pre-event may be stored in the sameor different buffers. Streams that are part of an event may be stored inthe same or different buffers. Streams that are part of supplementalinformation, a description, or a revision may be stored in the same ordifferent buffers. In one implementation, a buffer is coextensive withan MPEG-4 container.

A log is a list of records each describing a change and noting the timewhen the change occurred. Local logs 404 are updated on the occurrenceof a change in the configuration or operation of incident recorder 208and handset 132 (700). For example, local logs 404 may include an entryfor application of power to handset 132 (700), removal of power fromhandset 132 (700), switching video monitor 342 on or off, adjustment ofa time base used by handset 132 (700) (e.g. synchronization of time ofday, date), entry and exit from privacy mode (e.g., a privacy function),and adjusting or establishing parameters that affect recording orrevising (e.g., pre-event buffer length, video resolution for pre-eventor event, software upgrades).

Audio hub mike streams 406 include buffers for storage of audio for anyone or more of pre-events, events, supplemental descriptions, andrevisions.

Audio head mike streams 408 include buffers for storage of audio for anyone or more of pre-events, events, supplemental descriptions, andrevisions.

Audio oriented mike streams 410 include buffers for storage of audio forany one or more of pre-events, events, and revisions.

Audio handset mike streams 412 include buffers for storage of audio forany one or more of pre-events, events, supplemental descriptions, andrevisions.

Video oriented camera streams 414 include buffers for storage of videofor any one or more of pre-events, events, and revisions.

Supplemental documents 416 include buffers for text entry or scannedpaperwork for revisions.

Supplemental audio streams 418 include buffers for supplemental audiofrom the author-operator (spoken impromptu or in reply to an interactivevoice response script) for revisions. Supplemental audio streams 418 mayinclude audios streams for supplement information form all audio sourcesor from select audio sources. Supplemental audio information may beapportioned for storage in supplemental audio streams 418 and audio hubmike streams 406, audio head mike streams 408, audio oriented mikestreams 410, and audio handset mike streams 412.

Supplemental video streams 420 include buffers for supplemental videofor revisions. Supplemental video information may be apportioned forstorage in supplemental video streams 420 or video oriented camerastreams 414.

Menus 422 include legends that are displayed on display 730 of videomonitor 342. Legends may be responsive to a mode of operation of handset132 or 700.

Classification information 424 includes indicia of categories, suggestedgroups of categories, user defined categories, and associations ofcategories with information stored in other data structures 400 asdiscussed above. Classification information may be presented on display730 (e.g., categories) as legends 740 for selection by a user toclassify particular information. Classification information 424 maystore one or more associations of categories and information selected bya user or selected and classified automatically as discussed above.Indicia of classification may be included in an incident report orrevision. Classification information may be communicated to and/or fromshift hub 120.

Data 426 includes all variables and temporary storage required for theperformance of the program code 402. Data may further include deviceidentification for the component that stores the data structure (e.g.,handset 132 (700)) and for the primary subsystem to which it is a part(e.g., 208) or any or all of its components (e.g., personal hub 224(600), headset 222 (500)).

A handset includes any device that facilitates the capture of originalaudio and video information, capture of supplemental audio and videoinformation, review of captured information, and classification ofinformation. For example, handset 132 of FIGS. 1, 2, and 3 may beimplemented as shown in a perspective view of handset 700 in FIG. 7. Therear side includes terminals for connecting a battery charger of shifthub 120 to the battery (not shown) that is internal to handset 132(700). Conductor 612 for coupling to headset 500 and hub 600 extendsfrom handset 700. Handset 700 includes dedicated controls (750, 760,770, 720, 724) and touch-screen legends 740.

A user interface of handset 700 includes event handset mike 726, eventswitch 750, privacy LED 762, privacy switch 760, touch-screen legends740 along one edge of display 730, display toggle switch 770, powerswitch 720, handset speaker 722, and volume switch 724. Display 730 mayalso present original or supplemental information in apicture-in-picture (PIP) format 732.

The PIP format may be used to review any combination of two videostreams or other visual information such as scanned documents. Forexample, display 730 may present video (e.g., live from camera 510,video oriented camera streams 414) while PIP 732 presents supplementalvisual information (e.g., supplemental documents 416, supplemental videostreams 420, classification information 424).

Legends may be presented beside the movie or PIP presentation. Inanother implementation, the entire display area is used for the movie orPIP presentation.

Volume switch 724 operates to increase or decrease a volume of the audioprovided by speaker 722.

Cable 612 may be coupled to hub 600 or decoupled from hub 600 forstand-alone operation of handset 700. During stand-alone operation,handset 700 may be used to review original or supplemental informationand receive additional supplemental information via handset microphone726.

Display toggle switch 770 operates to turn display 730 alternately onand off as shown in state change diagram 820 of FIG. 8B. States of statechange diagram 820 include screen-on state 810 and screen-off state 812.While in screen-off state 812, display 730 does not display anyinformation. While in screen-on state 810, display 730 displaysinformation which may include original information, supplementalinformation, revisions, legends, warnings (e.g., low battery, hubdisconnected, headset disconnected), response to an IVR script, and anyother information. Successive operations of display toggle switch 770moves state change diagram 820 between the screen-on state 810 andscreen-off state 812.

Processor 340 of a handset 132 or 700 may implement a user interfaceaccording to various aspects of the present invention having particularsynergies for simplicity of operation. For example, when instructionsfor performing suitable methods are stored in memory 341 and performedby processor 340, the primary subsystem in which the processor, memory,and user interface is implemented performs state change mechanisms 800and 900 of FIGS. 8A and 9.

The state change logic as indicated in FIGS. 8A and 9 uses conventionalsymbology: an arrow is followed to change states when the processordetects the signal indicated beside the arrow. A state comprises theperformance of the one or more functions described for the state. Statesand state changes may be implemented with conventional hardware andsoftware (e.g., programming) technologies. Preferably, processor 340operates in only one state at any instant of time; however, state changemechanisms 800 and 900 may be implemented with additional functionsperformed in each of the illustrated states. Consequently, a mode ofoperation may include one state and may further include additionalfunctions performed while in that one state. Additional states may beimplemented between the illustrated states without departing from thestate change logic as illustrated in FIGS. 8 and 9.

Receipt of a signal may accomplish a transition from one state toanother state. A signal may be provided upon operation of a control. Forexample, an operation of event switch 750 (630) produces EVENT signaland an operation of privacy switch 760 (640) produces PRIVACY signal asshown in FIGS. 8A and 9.

Event switch 750 (630) and privacy switch 760 (640) operate to recordoriginal incident information in accordance with state change diagram800 of FIG. 8A. State change diagram 800 defines states of operation ofhandset 132 of FIGS. 1-3 and handset 700 of FIG. 7 while recordingoriginal information. States include pre-event recording state 802,privacy state 804, event recording state 806, and time, event recordingand mark (TEM) state 808. Operation continues in a state until allconditions are met for a state change.

Pre-event recording may also be referred to as pre-recording.

Entry into state 802 may occur on application of primary power (e.g.,power switch 720) to the handset or upon detecting that a touch screenicon has been actuated by the user.

While in pre-event recording state 802, handset 132 (700) captures audioand video information into a pre-event circular buffer as describedabove. The pre-event circular buffer captures information for a periodof time before overwriting information previously recorded in thepre-event buffer.

While in pre-event recording state 802, an operation of privacy switch760 (640) causes a state change to privacy state 804. An subsequentoperation of privacy switch 750 (640), prior to operation of any othercontrol, causes a state change back to pre-event recording state 802.

While in pre-event recording state 802, an operation of event switch 750(630) causes a state change to event recording state 806. A transitionfrom pre-event recording state 802 to event recording state 806 may alsooccur upon detecting a sudden acceleration of handset 132 (700).Generally, handset 132 (700) is worn or held by a user. Suddenacceleration of handset 132 (700) may indicate that an event hasoccurred that should be recorded. Events that may produce a suddenacceleration may include the operator rapidly accelerating from a stopand a force applied to the operator (e.g., physical blow, struck by abullet). A sudden acceleration of the handset may indicate a situationin which the user would like to operate event switch 720 (630), butphysically cannot. Acceleration may be detected and reported byaccelerometer 348.

While in privacy state 804, handset 132 (700) performs the privacyfunction and records no audio or video information. Although orientedcamera 510 and various microphones (520, 530, 620, 726) may continue toreceive video and audio information and provide signals responsive tothe video and audio information, no video or audio information isrecorded in memory 341. While in privacy state 804, privacy indicator762 (642) is illuminated (e.g., LED, lamp). In any other mode, privacyindicator 762 (642) is not illuminated.

While in privacy state 804, an operation of privacy switch 760 (640)causes a state change to pre-event recording state 802. While in privacystate 804, an operation of event switch 750 (630) causes a state changeto event recording state 806.

While in event recording state 806, handset 132 (700) captures originalaudio and video information about an incident. Event recording state 806captures audio information from handset mike 726 or hub mike 620, butpreferably from oriented mike 520 and head mike 530. Event recordingstate 806 captures video information from oriented camera 510. Processor340 stores captured information in memory 341 in data structures asdiscussed above.

While in event recording state 806, an operation of privacy switch 760(640) causes a state change to privacy state 804. While in eventrecording state 806, an operation of event switch 750 (630) causes astate change to TEM state 808.

While in TEM state 808, handset 132 (700) continues to capture originalaudio and video information; however, upon entering TEM state 808,processor 340 records a mark in the video and audio streams to indicatethat event switch 750 (630) was operated at that time during datacollection. An operator may insert a mark into a data stream duringrecording of the incident as a reminder to provide supplementalinformation about some aspect of the incident. A mark may be storedwithin a video or audio stream (e.g., same MPEG-4 container, differentcontainer, but related by time) or separately with information toprovide a correlation between the mark and the video or audio streams atthe time the mark was made.

Each entry into TEM state 808 records a new mark associated with thevideo and audio data being recorded at the time of entry. Whilereviewing, marks may be used as an index to the video and audio streams.Marks may be searched, sorted, and/or arranged in any manner tofacilitate review. Information presented for review may skip (e.g., fastforward, fast reverse, hypertext link) from a scene of a movieassociated with one mark to a scene of a movie associated with anothermark to speed access to information.

During review of previously recorded information, a list of recordedmarks (with or without descriptions) may be presented to assist incompleting a revision. A mark may be annotated to provide descriptiveinformation about the video and audio content at the time of the mark.After adding a description to a mark, a list of recorded marks may bepresented with descriptions to assist in reviewing. Descriptions mayinclude conventional thumbnails of the movie.

Upon entering TEM state 808, a timer is started. Operation of handset132 (700) remains in TEM state 808 for a duration of time (e.g., untilexpiration of a countdown timer). The state change that occurs after theduration of time depends on whether event switch 750 (630) was held(e.g., presses, activated, selected) for the duration of time or whetherswitch 750 (630) was operated and released prior to expiration of theduration of time. The duration of time may be for any amount of time,preferably a few seconds (e.g., 2-3).

Event switch 750 (630), privacy switch 760 (640), and the timer incooperation with event switch 750 (640) operate to cause state changesout of TEM state 808. While in TEM state 808, an operation of privacyswitch 760 (640) causes a state change to privacy state 804. While inTEM state 808, operating and holding event switch 750 (630) for theduration of time causes a state change to pre-event recording state 802.Operating but not holding event switch 750 (630) for the duration oftime causes a state change to event recording state 806.

The resolution of video information recorded in pre-event recordingstate 802 may be the same or less than the resolution of the videoinformation recorded in event recording state 806.

Event switch 750 (630) and privacy switch 760 (640) are operated tosupplement and classify original information (e.g., while reviewingpreviously recorded information) in accordance with state change diagram900 of FIG. 9. State change diagram 900 defines states of operation ofhandset 132 of FIGS. 1-3 and handset 700 of FIG. 7 while reviewingpreviously stored information. States include reviewing 902, supplementrecording 904, displaying categories 906, and recording classification908. Operation continues in a state until all conditions are met for astate change.

While in reviewing state 902, handset 132 (700) presents previouslyrecorded information on display 730 for review by the author-operator.Handset 132 (700) may further present marks stored during eventrecording. Marks may be presented to an author-operator as legends 740for selection by the operator. While reviewing, handset 132 (700) mayfurther provide audible interactive-voice-response (IVR) prompts andcorresponding legends 740 to receive an operator response via selectionof one or more legends 740 of display 730. Handset 132 (700) may furtherpresent suggested categories as legends during reviewing.

While in reviewing state 902, an operation of event switch 750 (630)causes a state change to supplement recording state 904. A subsequentoperation of event switch 750 (630) causes a state change back toreviewing state 902. While in reviewing state 902, an operation ofprivacy switch 760 (640) causes a state change to displaying categoriesstate 906.

While in supplement recording state 904, handset 132 (700) capturesaudio and video supplemental information from oriented mike 520, headmike 530, handset mike 726 or hub mike 620 and oriented camera 510.Supplemental information may provide additional information about theoriginal information being reviewed or other descriptive informationprovided by author-operator as described above. Supplemental informationmay be information provided responsive to audible IVR prompts. Anauthor-operator may provide a response to an IVR via head speaker 336,hub speaker 326, handset speaker 344, or legends 740 as described above.Supplemental information may include an audio description from theauthor-operator or activation of a touch-screen legend by theauthor-operator. Supplemental information is stored in memory 341.Supplemental information may be associated (e.g., same MPEG-4 container,point to an MPEG-4 container) to original information presented forreview.

While in supplement recording state 904, an operation of event switch750 (630) causes a state change to reviewing state 902.

While in displaying categories state 906, handset 132 (700) presentscategories for classifying information. Categories may be presented asIVR audio prompts or legends 740. An author-operator may select acategory to classify the information being reviewed or in advance ofrecording supplemental information. Processor 340 stores the categoryselected by the author-operator in memory 341. Classificationinformation (e.g., indicia of one or more categories and associatedinformation) may be stored in the same MPEG-4 container as theinformation being classified or in a separate data structure (e.g.,424). Examples of possible categories for classification are providedabove.

While displaying categories, any control 343 may be used to select acategory. In one embodiment, categories are presented as legends 740 andselection is performed by selecting a legend of legends 740. In anotherimplementation, categories are presented as an audio IVR list ofcategories and selection is performed by operation of a control 343,such as privacy switch 750 (630).

While in display state 906, selection of a category, whether by legends740 or operation of privacy switch 750 (630), causes a state change torecording classification state 908.

While in recording classification state 908, processor 340 storesindicia of one or more categories designated by the author-operator.Storing indicia of one or more categories may be accomplished asdiscussed above and may include encryption of the information associatedwith the category. Completion of recording the category causes a statechange to reviewing state 902.

An incident refers to human or animal activities and to a period of timewhen these activities take place. Incidents include, for example,formation of agreements, transactions, negotiations, discussions,ceremonies, meetings, crimes, attempted crimes, disagreements, assaults,conflicts, discoveries, research, investigations, and surveillance.Incidents may include consequences including changes to property such asimprovements, repairs, construction, production, manufacture, growth,harvesting, damage, loss, theft, burglary, arson, goods damaged inshipment, conditions of real estate, and/or conditions of agriculturaland forestry property. An incident may include damage to property and/orinjury to persons or animals. Damage to property or injury to persons oranimals may be accidental or brought on by the action or failure to actof one or more persons.

The factual description of an incident may aid others to determine theidentity of the property affected, and/or persons injured; identity ofwitnesses, law enforcement personnel, and anyone contributing to theloss or extent of the loss or the injury or extent of the injury; anychange in the property or change in the value of the property; and anychange in the condition of an object, person, plant, or animal.

The factual description of an incident may also be used to establishresponsibility for loss. For example, whether or not the facts of theincident require payment under an insurance policy may be determined onthe basis of the incident report. When a weapon is used in an incident,responsibility for the loss or injury may in part be based on whetherthe weapon is used within the guidelines of a law enforcement agency,guidelines set forth by a manufacturer of the weapon, or policies andreasonable behavior or negligence as determined by local customs,courts, and educational/training institutions.

A report of an incident in many cases is evidence of facts regarding theincident. Evidence may be needed for proof of performance under anagreement, resolution of failure to perform under an agreement, proof ofdamage, injury, or loss, or for enforcement of customs, rules,regulations, laws, judicial orders, or directives from superiors such asemployers, partners, custodians, guardians, relatives, officials, orhigher ranking officers. Foundation and corroboration support the use ofa report of an incident in court. Validation of an incident reportincludes verifying the accuracy and completeness of the foundation andcorroboration supporting the incident report.

Accurate and complete reporting of the facts surrounding an incident hasgreat social, economic, and judicial importance. Incident reporting aspracticed in the prior art has limitations that adversely affectaccuracy and completeness. More accurate and more complete incidentreports are needed and are provided by systems and methods according tothe present invention.

An incident report, as discussed herein, is a report of fact surroundingan incident. The incident report in a preferred implementation isintended to be admissible as evidence in court. The incident reportconsists entirely of information stored and communicated in one or moresuitable electronic formats. According to various aspects of the presentinvention, an incident report may include a combination of information(herein called incident information) including audio, photographs,video, forms, text, graphics, scans, detected signals, and electronicdocuments (e.g., email, word processing, spreadsheets, graphical models,photographs, equipment configuration data, equipment operation eventlogs). Scans include for example scanned paper documents (e.g., tickets,titles), scanned bar codes (e.g., on products, badges), scanned magneticstripes (e.g., bank cards, driver's licenses), scanned magnetic media(e.g. tapes, disks), scanned optical media (e.g., CDs, DVDs), andscanned glyphs (e.g., on documents, products, badges). Glyphs includesymbol marking and reading technologies (e.g., ECC200 DataMatrix, PDF417). Detected signals include intercepted remote control signals (e.g.,for mechanical and electrical equipment); intercepted communicationssystems simultaneously operating during the incident such as land linephones, cell phones, pagers, radios, tracking devices, mediabroadcasting stations, wireless and wired computer network links, andsources of interference with these systems; and measurements (e.g.,environmental sensors for temperature, sensors for hazardous conditions,monitors for physical conditions).

Incident information may include descriptions of the persons, animals,and things at an incident including, for example, subsystems brought tothe incident by law enforcement officers. These descriptions may becaptured in any convenient manner (e.g., recorded speech, video,photographs, scans of markings on things).

After the first incident information is recorded and available forreview, an incident report based on the incident information may bedeveloped through selecting, adding, supplementing, organizing,emphasizing, and editing any of which being referred to herein asrevising. The result of revising is herein called a revision. Eachrevision of an incident report may result in the creation of a newversion of the incident report. The prior version may be replaced by thenew version. Preferably, the original version is retained for comparisonand analysis with reference to the latest version. All versions may beretained. The incident information forming the basis for an incidentreport may be captured by an author who is operating a primary subsystemaccording to various aspects of the present invention, herein called anauthor-operator, or simply an operator. A primary subsystem, accordingto various aspects of the present invention, may facilitate any of thefollowing actions by the author-operator: timely developing one or moreincident reports, timely reviewing incident reports, and timely revisingof incident reports.

An incident report, in whole or in part, may be presented to a user on aprimary subsystem of the present invention that includes a displayand/or on a workstation of a secondary subsystem. The secondarysubsystem may include an evidence manager. The user of an evidencemanager may obtain summaries of numerous incident reports using databasequery and reporting technologies and may view the results on theworkstation. The incident report may be the subject of a predefined workflow. Any conventional work flow management process may be used tocomplete, validate, and/or authorize use of the incident report. Thesefunctions may be accomplished by different individuals along the workflow being managed. Portions of an incident report may be managed inconverging work flows that produce a combined incident report in a newversion.

Any source of information may contribute to an incident report throughoperation of a primary subsystem, according to various aspects of thepresent invention. The incident information (herein also called data)may include what was seen, heard, or understood by the author-operator.Sources of information may include detectors of any of the incidentinformation discussed above.

Recordings from these sources of information, unfortunately, may notcapture all of what was seen, heard, or sensed by the author-operatorand/or unambiguously show how the author-operator would interpret whathappened. Due to the frailties of human memory, the humanauthor-operator in many cases has a diminishing ability over an extendedperiod of time to recognize ambiguity in the recording and/or omissionsfrom the recording and to supply information that would resolve theambiguity or explain the omission.

To avoid such loss of ability and to improve the accuracy of incidentreports, systems and methods of the present invention may provide thecapability to the author-operator to review and to supplement what wasinitially recorded. In other words, systems and methods according tovarious aspects of the present invention may employ structures andoperations that facilitate supplementing recorded information withadditional information that is generally recorded at a time soon afterthe initial incident recording is made. The result of supplementing isalso referred to herein as a revision. More complete and more accurateincident reports result.

As discussed herein, recording and supplemental recording may beaccomplished with any suitable recording technology or combination ofsensing, detecting, formatting, communicating, and recordingtechnologies. As used herein, a first type of presentation of audioand/or video content (herein also referred to as a movie) plays for aduration during which an operator may indicate an instance in time for asecond presentation (herein also referred to as an excerpt) of arelatively short duration (herein also referred to as a scene). Theshort duration may limit the playing of the second presentation to astill photograph from the video content with no audio. The shortduration may be somewhat longer but limit the playing of the secondpresentation to a loop showing one or a few movements. The shortduration may be long enough for the operator to perceive from theexcerpt of the first presentation some of the audio (e.g., a gunshot, afew words) and some of the motion (e.g., a glance, a facial expression)of the first presentation. By analogy to video information, any otherform of incident information may constitute a movie and/or a scene andbe supplemented by the author-operator.

The first presentation is discussed herein as consisting of a sequenceof scenes, though a scene may have any suitable duration, notnecessarily uniform for all scenes throughout the first presentation.And, the second presentation is discussed herein consisting of one sceneof any suitable duration, but identified to a particular instance oftime. The instance of time may correspond to the beginning of the scene,the end of the scene, or any convenient instance during the relativelyshort duration of play back of the scene.

In a preferred implementation, recording and supplemental recordingproduce information that is stored, reviewed, revised (e.g.,supplemented), and communicated in accordance with “Coding of MovingPictures and Audio”, an ISO/IEC standard, known as MPEG-4. In accordancewith MPEG-4, video information and audio information are stored in ahierarchy of containers. Information recalled from these containers maybe used to compose scenes and movies for presentations as discussedherein.

Systems for collecting and managing evidence, according to variousaspects of the present invention include subsystems generally used atthe time and place of the incident (herein called primary subsystems)and other subsystems that are generally used not at the time or place ofthe incident (herein called secondary subsystems). These subsystemscooperate as a system for collecting and managing evidence.

Cooperative functions include functions performed by both primary andsecondary subsystems in cooperation. Cooperative functions includeidentifying the author-operators of primary subsystems before evidenceis collected, arranging for primary subsystems to cooperate before,during, and/or after incidents, and transferring collected evidence fromthe primary subsystems to the secondary subsystems.

Primary subsystems may perform any one or more of the followingfunctions in any suitable combination: launching and/or deploying aforce (lethal or less lethal) to a distant suspect to attempt todiscontinue the present behavior of a person or animal (herein called atarget), stimulating the target with an electrical current throughtissue of the target to interfere with voluntary use by the target ofits skeletal muscles (herein called electrical stimulation), loggingevents related to launching and/or stimulating, detecting for collectingevidence, recording for collecting evidence, revising recorded evidence,communicating among components identified to the same operator (hereincalled a personal primary subsystem), communicating among primarysubsystems, communicating between a primary subsystem and a secondarysubsystem, storing the identity of the operator, storing addresses forcommunication, receiving software and data from a secondary subsystem,and transmitting status, data, and evidence to a secondary subsystem.

Some primary subsystems have a central function that contributes to aunique name or type (e.g., launcher, projectile, stimulator, datalogger, detector, collector, recorder, display, editor, transceiver,hub, store, identifier, reporter). However, combinations may not beamenable to a single name (e.g., combination launcher-stimulator-datalogger, combination recorder-editor-transceiver-reporter). Consequently,the term primary subsystem is used herein to describe an apparatus thatimplements any one function and any apparatus that implements anycombination of functions.

A primary subsystem may be packaged in several units (e.g., productsindividually sold or handled) (herein called components) that cooperateby wired or wireless links to participate in the set of functions of theprimary subsystem. A component may be capable of operation for somefunctions without communication as part of the primary subsystem (e.g.,providing a device identity to a device identification detector).

Secondary subsystems may perform any one or more of the followingfunctions in any suitable combination: preparing components of primarysubsystems for reassignment and reuse, detecting the identification of aperson to be assigned the role of an operator for one or more componentsof a personal primary subsystem, detecting the identification ofcomponents to be part of a personal primary subsystem, transmittingidentification information to components of a personal primarysubsystem, detecting the identification of additional primary subsystemsand associating with each additional primary subsystem an operatoridentification and/or a personal primary system identification,transmitting identification information to the additional primarysubsystems, determining the identification of a primary subsystem forthe purpose of receiving evidence from it, receiving evidence, storingevidence, and managing evidence. Suitable groups of these functions maybe part of a general provisioning process that includes check-out, andcheck-in of persons, components, primary subsystems, and incidentreports.

Communication, according to various aspects of the present invention,includes communication between the components of a personal primarysubsystem, between primary subsystems, and between primary subsystemsand secondary subsystems. Communication is discussed herein withreference to a link between communicating subsystems or a link betweencommunicating components of subsystems. The link generally includes achannel and protocol suitable for the information being communicated.The channel may have frequency and/or timing criteria for receivingand/or transmitting. The channel may be wired or wireless. A dedicatedwired channel may include receiving without an address and/ortransmitting at any time. A shared wired channel may employ channels andprotocols similar to a wireless channel. A wireless channel may bededicated and if so, communication may be analogous to a dedicated wiredchannel. Otherwise, the protocol organizes competition for use of thechannel for transmitting and receiving only according to an address. Asubsystem may respond to one address or to several addresses. An addressmay be unique to one subsystem or general (e.g., group addressing) toseveral subsystems or to all subsystems. Addressing may include groupaddresses for example for anonymous transmitting and/or simultaneousreceiving of a broadcast to several subsystems. A transmitting protocolmay permit transmitting at a random time (beacon), at a random timeafter receiving (polled), at a prescribed time (dedicated slot), and/orat a prescribed time after receiving (assigned slot). A transmitter of afirst subsystem may transmit and a receiver of a second subsystem mayreceive a command to stop transmitting by the second subsystem for anarbitrary or a predetermined period of time.

An operator may collect evidence single-handedly using his or herpersonal primary subsystem. For example, an operator may navigate aroute and record the status of equipment and security mechanisms such aslocked doors and appropriate lighting.

Operators may attend incidents and collect evidence in teams. Each teammember may be an operator as to his or her personal primary subsystemand be identified to a suitable extent for operation or coordinationwith other primary subsystems. For example, each team member may haveweapons (primary subsystems) for electrical stimulation as discussedabove. Each team member may be associated to other team members' weaponsto enable each team member to control the stimulation applied by anyother team member's weapon.

A primary subsystem that logs events and/or detects incident informationand further communicates directly or indirectly with a secondarysubsystem is herein called a data source. A data source in variousimplementations may also record incident information, revise incidentinformation, communicate between components of the data source usingwired or wireless links, and/or communicate with another primarysubsystem.

A data source may be located permanently at the location of the incident(e.g., a security camera, an entrance interview microphone, a documentscanner, an access control system) and may communicate as discussedabove (e.g., via a wired network among data source components). Typicaldata sources for law enforcement include red light and excess speedtraffic monitoring systems. Data sources related to facility securitymay include badge readers, video surveillance, audio surveillance,biometric identification systems, and detectors of ambient conditionsand changes in ambient conditions. For example, ambient conditions mayinclude temperature, vibration, audible and visible indications ofstatus quo in an environment subject to surveillance.

Changes in ambient conditions may include indications of entry by aperson or animal trespassing, passersby, and any disruption of normaloperation of equipment in the facility or surrounding area. Equipmentbeing monitored by a data source may provide measurements and/or statusreporting. A data source adapted to receive information from equipmentmay receive such information by monitoring observable equipmentconditions and electrical communication to and from the equipment. Forexample, operation of an elevator in the vicinity of an incident may beobserved or the signals that operate the elevator may be detected.

Data sources may be brought to the location of an incident by victims,witnesses, accomplices, suspects, and/or law enforcement personnel. Datasources may be overt or covert. Such equipment may include police patrolcar on-dash video and audio systems, audio and video equipment worn bypersonnel, cellular telephones with video recording capability, andconventional crime scene investigation equipment (e.g., forensic datagathering measurement and analysis systems).

A primary subsystem that stimulates tissue of a target and/or launchesor deploys a force toward a target is herein called an electricalstimulation device or electronic control device (ECD). An ECD mayfurther include a data source having any suitable combination ofcapabilities identified above to a data source. Weapons (e.g., ECDs) maybe either fixed or portable. Fixed weaponry may include turret-mountedweapons attached to facilities and/or land mines. Portable weaponry mayinclude handguns, rifles, batons, grenades, missiles, electronic controldevices, and electrified projectiles (e.g., electronic control devicesand electrified projectiles as manufactured, for example, by TaserInternational, Inc. as models M26, X26, and XREP, the publishedspecifications and user manuals for which are hereby incorporated bythis reference without limitation of the present context).

For example, a primary subsystem comprising a weapon and a data sourcemay include a laser target designator or sight, an illuminator toilluminate the target, a video recorder aimed at the target, amicrophone aimed at the target, an electrical stimulation circuit,projectiles, and a propellant for deploying projectiles for theelectrical stimulation. Such a primary subsystem may be referred to as aweapon due to its central force function. The primary subsystem maytransmit status signals and/or log its status and usage information(e.g., store time stamped event records). Consequently, the primarysubsystem may transmit and/or record audio of ambient conditions, speechof the target, speech of witnesses and/or weapon operator, and/or videoof the target. The primary subsystem may record and/or transmit stillphotographs. The primary subsystem may record and/or transmit streamingvideo. For example, video may begin at a time tens of seconds beforeoperation of a trigger of the weapon and extending tens of seconds or afew minutes after operation of the trigger.

A primary subsystem may record and/or transmit the location of theincident. A primary subsystem may detect the Earth's magnetic field(e.g., azimuth), including compass bearing information in or associatedwith audio and/or video recordings. A primary subsystem may detectorientation in linear or polar coordinate systems (e.g., pitch, roll,velocity, acceleration, momentum, angular momentum). Location may bedetermined by a detector of the primary subsystem using a globalpositioning system (GPS). A GPS receiver may be incorporated in aprimary subsystem (e.g., a data source, a combined weapon and datasource).

A data source may be used for scanning, detecting signals, and foraccessing documents, as discussed above. Scanning, detecting, and/oraccessing may be for the purpose of including relevant information in anincident report. For example, the contents of a person's wallet may bescanned by a data source for collection of identifying materials.Paperwork related to licensing of a facility or operation of a vehiclemay be scanned. The audio and video portion of a telephone or internetcommunication may be captured. Email, text messages, and audio messagesplayed back from a telephone answering machine may be captured by a datasource.

A primary subsystem may include a detector, a recorder, a transceiver,and a user interface for reviewing and revising an incident report. Adetector may detect any ambient condition: video, audio, communicatedinformation (e.g., eavesdropping), and/or scanned information. A videodetector may include a video camera oriented by the author-operator forrecording what is in the field of view of the author-operator.

A primary subsystem may format detected information for the purpose offorming recorded media and/or for communicating recorded information.Preferably, detected information is formatted for supplementing anincident report by the author-operator of the data source (e.g., viaMPEG-4 format). The transceiver may receive detected information fromthe detector for communication in real time. The recorder may supplyrecorded and/or revised information to the transceiver for communicationvia a link to other primary subsystems (e.g., for review and revision bya team member) and/or a secondary subsystem. The transceiver may includeany conventional radio, telephone, or digital network transceiver. Inone implementation, the transceiver supports a link to an ad hoc networkfor communication with primary and/or secondary subsystems. The userinterface may facilitate preparing and/or revising an incident reportfrom the information recorded by the recorder.

The user interface may include a display and controls adjacent to thedisplay. The display may provide legends arranged along an edge of thedisplay. User-operated switches may be arranged along the edge of thedisplay and be identified for the purpose described by the legends.Requested information may include true/false or multiple choice prompts.A reply to such a prompt may be made by the operator by operating aswitch on the edge of the display, a voice response by the operator, oroperation of a pointer control that is part of the user interface.

A primary subsystem may interact with a human source of information,generally its author-operator. Interaction may include the presentationof questions, suggestions, or requests for narrative. The user interfacemay present information to the user in visual (on a display) and/oraudio form (by Interactive voice response (“IVR”)). The author-operatormay respond via the user interface (operating controls and/or givingaudio and/or video replies) to provide the requested information.Requested information may be organized as a hierarchy of diagnostics.Each diagnostic may be a request for information, a question (e.g.,multiple choice or true/false, or a request for specific name, date,age), or a request to confirm information. The sequence of diagnosticsmay be predetermined by the primary subsystem. A primary subsystem mayinterpret an answer provided by its author-operator and conditionallydetermine whether another hierarchy (or sub-hierarchy) of diagnostics isto be presented. The interaction with the operator of a data source may,therefore, be guided by prompts provided by the primary subsystem. Theprompts may differ depending on the type of incident being reported, thetype of primary subsystem, and/or answers by the operator. Diagnostichierarchies in one implementation include IVR scripts.

A secondary subsystem includes any computer system (e.g., personalcomputer, server, network of servers) that receives data from one ormore primary subsystems and stores, manipulates, or reports the data useas evidence. A secondary subsystem may receive data as an incidentreport. A secondary subsystem may store, select, decompose, classify,sort, combine, compare, analyze, adjust, organize, and/or control accessto incident reports. A secondary subsystem may comprise a hierarchy ofcomponents.

Methods, according to various aspects of the present invention, increasethe likelihood that the incident report is complete, accurate,corroborated, verifiable, accessible, integrated with other sources ofinformation, and reliably stored for use as evidence. These functionsand advantages may be obtained by virtue of the variety of elements ofan incident report (e.g., sounds, movies, forms, text, graphics,signals, documents, scans) and the capability of revising a scene basedon any or all of these by the author-operator of the primary subsystem.Each element of incident information in an incident report or revisionmay be raw or derivative (e.g., presenting valuable selection andorganization of clippings, croppings, enhancements, cross-correlations,sequences, sets, chronologies, related opinions, proofs, syllogisms,predictors of outcomes, and logical outcomes).

Generally two elements are associated logically or physically. Two ormore elements may be associated. The association may be physical, forexample, when reference to elements or elements themselves are stored inthe same physical record. Association may be logical when a query ofrecords that meet a given relationship produces a report indicating therelationship holds for the subject elements. An association in theterminology used for database management may be called a tuple.According to various aspects of the present invention, tuples ofinformation provide the solutions to problems and benefits describedabove. For instance, an incident report may include a tuple of weaponusage information, video information, and responses gathered during aninterview with a human source of information. For instance, a video clipmay be associated with a date and time of a trigger pull of a weapon(e.g., an electronic control device), and an audio description of thebehavior of the target (e.g., a suspect or animal) as provided by a lawenforcement officer in response to a prompt to describe the target. Asanother example, an audio clip may be substituted for the video clip inthe previous example. Still another example, a video clip may beassociated with an audio supplementary description and a response by anofficer describing the behavior of the target. As discussed above, videoinformation, weapon information, and interview responses may beassociated in a single primary subsystem, in a primary subsystemoperating as a hub or master of primary subsystems reporting to thesecondary subsystem, or in a secondary subsystem that receives fromindividual primary subsystem the individual data items prior toassociation. The basis for association may be an incident identifier ora consequence of concurrent acquisition of the data at the primarysubsystems.

Data structures, according to various aspects of the present invention,may implement tuples, as described above. A data structure may be storedas a record of a database. A data structure may exist temporarily inmemory referred to by process performed by a work flow processor. A datastructure may include the tuple of elements and other data. The tuple ofelements may include, for example, meta-data, time of day, officeridentification, weapon identification, identification of otherindividuals or animals appearing or observable from the audio and/orvideo data, identification of the camera used to record video,identification of the audio of the microphone used to collect the audioinformation, identification of the weapon and its configuration whichprovides weapon usage information, as well as preliminary results ofstatistical analysis. Preliminary results may include conclusions as toapplicable weapon usage policies, applicable guidelines for datacollection or for weapon usage, meta-data, index ordinals, descriptionof location, descriptions of jurisdiction, and other information thatapplies to the incident though may not have been readily available inreal time or recorded during the period of time covered by the incident.

The data transferred to a secondary subsystem, according to variousaspects of the present invention, includes revisions made by anauthor-operator of the primary subsystem.

Revisions may improve the emphasis or clarity of an incident report.Video images may be cropped, panned, and/or zoomed. Movies may beclipped. Photographs may be cropped and/or scaled. Audio streams may beclipped. Printed information may be amended or partially rewritten forclarity. All of these revisions may occur at the primary subsystem byoperation of a user interface. The time the revision was made may alsobe recorded. The original recordings are preferably retained and therevisions incorporated in a new version of the incident report.

An incident may initially be identified by a date and period of timeduring which the incident and/or investigation of the incident occurred.Any conventional identification may also be used. Each primary subsystemmay be made aware of the incident identifier. For example, primarysubsystems with reasonably synchronized date/time clocks may simply adddate/time stamps to the information they provide. Primary subsystemshaving a user interface may accept an incident identifier from a user.

An incident report may be supplemented with a report of all time keepingdevices used at the incident and recorded in incident reports. Thereport of all time keeping devices may be made at one instant of timefor comparing relative time discrepancies. The report may be made atseveral times where each device is compared to a reliable time base.Devices that lack electronic communications may be included withsuitable user interface prompts and controls (or recordings). Forexample, a prompt could ask the operator to verbally recite the time ofday on his or her wrist watch.

For indirect transfer of data from a primary subsystem, the primarysubsystem may include removable memory (e.g., semiconductor memory,magnetic tape or disk, optical media). A secondary subsystem may includea suitable reader for the removable memory. The primary subsystem mayinclude a wired or wireless communication capability for direct transferof data from removable or non-removable memory to the secondarysubsystem. For example, the system for evidence transfer and managementmay include a docking station and/or a transceiver each for receivingdata from a primary subsystem.

Evidence management may include validation of data received from aprimary subsystem (e.g., incident reports and revised incident reports),making further revisions (e.g., creating derivative incident reports),combining portions of two or more incident reports, and comparingincident reports. Any data format may be used for transfer into asecondary subsystem. Any data format may be used for storing data in asecondary subsystem. Particular synergies are realized, according tovarious aspects of the present invention, when only a few, or one, dataformat is used for all data transfer and storage functions of thesecondary subsystem. Preferably, both transfer and storage use a formathaving most if not all of the structures and functions of MPEG-4.Combining may be accomplished, for example using MPEG-4 objects,descriptions, and metadata, by including in a revision objects,descriptions, and/or metadata that originate from more than one primarysubsystem.

The functions of a secondary subsystem as discussed above may bearranged for convenient use by diverse personnel responsible fordifferent portions of collecting and managing evidence. All functionsrelated to primary subsystems and their operators may be accomplished ata first location and all other functions (e.g., evidence storage andanalysis) may be accomplished at a second location. For example, asystem for collecting and managing evidence may include any number ofstation hubs coupled by a network to any number of shift hubs. A stationhub provides secure operation of an evidence manager. A network supportsdata and inter-process communication. Any conventional protocol may beused (e.g., an Internet or intranet protocol stack). A shift hubprovides data transfer from a primary subsystem (e.g., incident recordsand revisions) and may further provide physical storage (e.g., off-shiftsecure storage for personal items or items controlled by an armory),recharging of rechargeable batteries, and/or data transfer to theprimary subsystem (e.g., software upgrades, information regardingtactical tasks, evidence collection tasks, and communication tasksdiscussed below with reference to FIGS. 16 and 17).

For example, a system for collecting and managing evidence 1000 of FIG.10 includes station hub 1010 coupled by network 1014 to shift hub 1020.Station hub 1010 hosts evidence manager 1012 (e.g., a database manageradapted in a conventional manner for managing evidence as discussedherein). Hosting includes a conventional secure computing environment(e.g., physical security, communication security, access controls,encryption). Network 1014 provides secure communication between anynumber of station hubs 1010 and shift hubs 1020. Shift hub 1020 includesa processor 1020, an ad hoc transceiver 1024 for wireless communicationwith any suitable number of primary subsystems equipped for wirelessdata transfer, docks 1026 for wired connection to any suitable number ofprimary subsystems, a device identification detector 1028, and a personidentification detector 1029.

Processor 1022 via ad hoc transceiver 1024 and/or docks 1026 may pollprimary subsystems (and/or components) that are within range formaintaining among them an ad hoc network based on one or more suitablecommunication channels (e.g., conventional IR, radio, or wirelessnetwork channels) and based one or more suitable communication protocols(e.g., conventional IEEE 1702). Such a network is “ad hoc” becausecandidates of the network may enter and members of the network may exitthe zone of communication (e.g., moved by humans) without advance noticeto processor 1022. Processor 1022 recognizes entries and exits andmaintains the ad hoc network with as many members as practical for thecapability of processor 1022.

An ad hoc transceiver may participate in different ad hoc networks atdifferent times. For instance, an ad hoc transceiver not at an incidentmay join an ad hoc network for transfer of incident reports to asecondary system (e.g., 1032 in FIG. 10). The ad hoc transceiver may, atanother time, join an ad hoc network for recording incident information(e.g., 1032 in FIG. 11). The ad hoc transceiver may, an another time,join an ad hoc network for directing tasks to other primary subsystems(e.g., 1260 and 1109 of FIG. 16). In other implementations differenttransceivers may be used for some or all of these types ofcommunications to accommodate differences in channels and/or protocols.

A device identification detector detects an identification of acomponent to a primary subsystem or of an entire primary subsystem(e.g., a personal primary subsystem). For example, on check-in to shifthub 1020 (e.g., docking or local ad hoc communication) of a component ofor for a primary subsystem, suitable components of the primary subsystemthat are plugged into docks 1026 may be identified by deviceidentification detector 1028 to the incident reports transferred fromthe components for purposes of evidence validation. On check-out fromshift hub 1020 (e.g., undocking) of a component for a primary subsystemremoved from docks 1026, the component that is removed from docks 1026may be identified to the primary subsystem (e.g., in the same or anothercomponent) so that incident reports are recorded in association withthat component's identification, again for purposes of evidencevalidation.

A person identification detector detects an identification of a personassociated or to be associated with a primary subsystem. For example, oncheck-in to shift hub 1020 (e.g., docking or local ad hoc communication)of a primary subsystem, the person that plugs suitable components of theprimary subsystem into docks 1026 may be identified by personidentification detector 1029 to the incident reports transferred fromthe primary subsystem for purposes of evidence validation. On check-outfrom shift hub 1020 (e.g., undocking) of a primary subsystem from docks1026, the person that removes components of a primary subsystem fromdocks 1026 may be identified to the primary subsystem so that incidentreports are recorded in association with that person's identification,again for purposes of evidence validation.

As discussed below with reference to FIGS. 16 and 17, activators 1260and electronic control devices 1270 may be plugged into docks 1026 orcommunicate via ad hoc transceiver 1024 to exchange addresses foraddressable stimulus control. Processor 1022 may read such addressesstored in a first activator and write those addresses into a secondactivator. Processor 1022 may receive addresses for stimulus control vianetwork 1014.

Device identification detector 1028 may detect an identification forobtaining addresses for addressable stimulus control, discussed belowwith reference to FIGS. 16 and 17. For example, weapons that respond tosignals for addressable stimulus control (e.g., electrified projectiles)may be identified to identification detector 1028 by bar codes, glyphs,or radio frequency identification (RFID) technologies. The weaponidentification may directly or indirectly determine addresses needed fortransfer into an activator. As another example, persons (e.g.,operators) intended to use an activator with particular weapons thatrespond to signals for addressable stimulus control may be identified toperson identification detector 1029 in any conventional manner (e.g.,badge reader, biometric detection). Addresses for stimulus control maybe associated with an intended operator identification.

The association of an intended operator identification with one or moresuch addresses may be accomplished by a user interface of shift hub 1020(not shown) or by a user interface coupled to network 1014 (not shown)for example used by an armory when dispensing electrified projectileshaving addresses for stimulus control. The armory may specify addressesfor stimulus control of those electrified projectiles being dispensed inassociation with an identification of an activator and/or in associationwith an identification of a person chosen to use an activator. As partof check-out of an activator (undocking) to an identified person, theactivator may receive (prior to undocking or by ad hoc communication)addresses for stimulus control suitable for the identified person.

Docks 1026 accept, by plug-in to a wired network, any suitable number ofprimary subsystems and/or components thereof. Docks may also provide alocation (e.g., a bin) within range of ad hoc transceiver 1024 forcommunication between processor 1022 via transceiver 1024 and any numberof primary subsystems and/or components thereof placed at the location(e.g., in the bin). The location may be suitable for detecting deviceidentification by device identification detector 1028. For example, handsets 1032 and 1034, activator 1260 and ECDs 1110 may be plugged intodocks 1026. Head sets 1122, personal hubs 1124, and ECD projectiles 1270may be located in a bin (not shown) for scanning and/or programming bydevice identification detector 1028.

Docks 1026 locates and/or links for communication components and primarysubsystems for data transfer to secondary subsystem 1010 as coordinatedby processor 1022 and evidence manager 1012. Data transfer may includeincident reports and/or usage logs. If other components and/or primarysubsystems are nearby but not plugged into docks 1026, data transfer mayoccur via ad hoc transceiver 1024 as controlled by processor 1022 forcommunication with those other components and primary subsystems.

Components and primary subsystems may be recharged via docks 1026. Forexample, hand sets 1032 and 1034, activator 1260 and ECD 1270 may beplugged into docks 1026 for recharging of their internal batteries ascontrolled by processor 1022. Processor 1022 may notify an operator ofsystem 1000 of undocked components and primary subsystems that maybenefit from docking (e.g., higher reliable data transfer rate,recharging).

Each primary subsystem (e.g., hand set, activator, ECD projectile) thatcooperates with shift hub 1020 may receive from shift hub 1020 dataidentifying an intended operator for the primary subsystem (e.g., fromperson identification detector 1029). Identification of the intendedoperator may then be added to data recorded by the primary subsystem(e.g., identifying the author-operator) for purposes of laying afoundation for the incident record as evidence. Any or all components ofa primary subsystem may be identified to any or all of the othercomponents of the primary subsystem (e.g., using a unique primarysubsystem identifier and/or a unique ad hoc address for the primarysubsystem).

The functions of a shift hub may be reduced to cooperate with anothersecondary subsystem component (not shown) herein called a locker dock.For example, the reduced shift hub includes one or more ad hoctransceivers 1024, and processor 1022 and omits docks 1026, deviceidentification detector 1028, and person identification detector 1029.Numerous locker docks (not shown) are connected by network 1014 to oneor more reduced shift hubs. Each reduced shift hub connects by network1014 to station hub 1010. Each locker dock is located in an identifiedperson's locker generally used for personal effects when the person ison duty. The locker dock includes processor 1022, docks 1026, and deviceidentification detector 1028. Those devices that cannot be identified byplugging into docks 1026 are identified by device identificationdetector 1028.

A device identification detector may scan (e.g., optical reader,magnetic reader) or receive (e.g., radio link, IR link) from a device anidentification. A device identification detector may change orsupplement the identification of a device. For example, the deviceidentification may be replaced, added to, or revised by any mannersuitable for human and machine readable identification (e.g., mark,print, erase, magnetize, re-magnetize, transmit into). Theidentification from or to the device may include a unique address, agroup address, or any combination of one or more of these addresses.

A hypothetical incident and application of systems and methods accordingto various aspects of the present invention is illustrated in FIG. 11.FIG. 11 is a pictorial representation of a hypothetical incidentinvolving two law enforcement officers 1106 and 1104 apprehending asuspect 1102 while each officer is operating a respective primarysubsystem, herein called a system for incident recording 1109, 1108(also called an incident recorder), according to various aspects of thepresent invention. Officer 1104 operates an electronic control device1110 (e.g., a TASER International model M26 or X26) that deploys twowire-tethered darts that hit the suspect 1102 at contact points 1112 and1114. Current generated by the electronic control device flows throughthe wires, darts, and tissue of the suspect to cause involuntary musclecontractions, halting locomotion by the suspect and facilitating arrestof the suspect. System for incident recording 1108 worn by officer 1104records a movie (e.g., audio and video) during the confrontation. Systemfor incident recording 1109 worn by officer 1106 also records a movieduring the confrontation, from a different point of view. Systems 1108and 1109 are identical; each includes a head set 1122 (1132), personalhub 1124 (1134), hand set 1032 (1034), and on-duty transceiver 1128(1138). Each headset 1122 (1132) includes a camera and microphoneoriented away from the officer toward the field of view of the officer'seyes. Soon after suspect 1102 is arrested (e.g., hand cuffed, shackled,confined), officer 1104 (1106) may independently review the movie thatwas recorded and add descriptions to any scenes. Reviewing isaccomplished by removing the hand set from the personal hub and watchingthe movie on a display of the hand set. Adding a description isaccomplished, among other things, by identifying a scene, and addingaudio (e.g., talking about the scene into a microphone of the head setor personal hub), adding video (e.g., removing the camera from theheadset and orienting it toward anything of interest), and/or addinggraphical information (e.g., describing in a standardized way where onthe body of the suspect contact points 1112 and 1114 occurred). Whilethe hand set is apart from the personal hub, the officer may use amicrophone and speaker of the personal hub for communication via theon-duty transceiver, for example to a dispatch agent.

In an exemplary implementation, a system for incident recording (hereinalso called a primary subsystem, a personal primary system, or anincident recorder) 1108 of FIG. 12 includes hand set 1032, on-dutytransceiver 1128, personal hub 1124, and head set 1122. Handset 1032includes processor 1240, memory 1241, video monitor (also herein calleda display) 1242, controls 1243, ad hoc transceiver 1244, audio incircuit 1245, audio out circuit 1246, and local link transceiver 1247.On-duty transceiver 1128 includes transmitter 1212 and receiver 1214.Personal hub 1124 includes push-to-talk circuit 1222, hub microphone1224, hub speaker 1226, mixer 1228, mixer 1230, and local linktransceiver 1232. Head set 1122 includes head microphone 1234, headspeaker 1236, oriented microphone 1235, oriented camera 1237, andorientation detector 1238. The functions and functional cooperation ofthese components are discussed below.

A hand set, according to various aspects of the present invention,provides a display and provides controls sized and positioned foroperation by a user's fingers and/or thumbs and operates to supplementrecorded information with a description determined (e.g., created,defined, selected, specified) by the user. The description (also hereinreferred to as a supplement, supplemental information, and/or arevision) may include additional video information, audio information,graphics information, text, status, logs, measurements, calculations,documents, and/or data. A hand set may further include the structuresand perform the functions of a data source as described herein. A handset may record information. A hand set may receive information to berecorded by the hand set. A hand set may communicate recordedinformation and/or supplemental recorded information to other portionsof an incident recorder and/or to a system for evidence transfer andmanagement system. For example, hand set 1032 receives from personal hub1124 signals that convey audio and video information and records theaudio and video information in MPEG-4 format in memory 1241. In anotherimplementation, personal hub 1124 and on-duty transceiver 1128 areomitted and hand set 1032 cooperates directly with head set 1122 througha wired or wireless interface. In another implementation, head set 1122is omitted and hand set 1032 includes a microphone and speaker for useby the author-operator of the hand set and an oriented microphone andoriented camera that are oriented by the author-operator of the handset.

An on-duty transceiver provides inter-personal communication. An on-dutytransceiver may provide coordinated communication among persons workingtogether to collect evidence. An on-duty transceiver may supportcoordinated communication among persons for surveillance and security,law enforcement, and/or military operations. Communication may be in anysuitable conventional form. An on-duty transceiver may provide 2-wayhalf duplex audio communication via radio. In another implementation, anon-duty transceiver provides in addition to radio or in place of radio,full duplex cellular telephone communication. In another implementation,an on-duty transceiver provides audio and or video communication viawireless computer network technologies. For example, on-duty transceiver1128 includes 2-way half duplex audio communication via radio ondedicated emergency response and police channels.

A personal hub, according to various aspects of the present invention,couples one or more of an on-duty transceiver and a head set to a handset. A personal hub may cooperate with an on-duty transceiver to provideaudio input and output transducers located for convenience near theauthor-operator's mouth and ears. A personal hub may include a wiredinterface or a wireless interface to a head set. A personal hub mayprovide a wired interface or a wireless interface to a hand set. Forexample, personal hub 1124 provides a wired interface to on-dutytransceiver 1128, provides a push-to-talk switch for use with on-dutytransceiver 1128, supports a microphone and speaker in the personal hubfor use with on-duty transceiver 1128, provides a wired interface tohead set 1122, and provides a wireless interface to hand set 1032. Inanother implementation, personal hub 1124 includes one or more detectorsand/or one or more recorders as discussed above with reference to a datasource.

A head set, according to various aspects of the present invention,supports an oriented detector for orientation (e.g., movement) by theauthor-operator to detect from the same direction from which theauthor-operator's senses detect. A head set for a human author operatorand for at least one of audio and/or video detecting is sized for beingworn by the author-operator on his or her head. A head set may include,as an oriented detector, a microphone for detecting sound coming towardthe author-operator. A head set may include, as an oriented detector, acamera for detecting radiant energy in any suitable channel or spectrum.A head set may include a source of radiant energy and a detector ofradiant energy from the source that is reflected back toward the headset. A head set may include a laser for identifying a reference locationand/or for use as a designator for focusing data sources and/ortargeting weapons. For example, head set 1122 is designed to be worn ona human operator's head. Head set 1122 includes an oriented microphoneand an oriented camera for continuously detecting audio and visual (orinfrared) information from the direction the operator turns his or herface. Head set 1122 includes an orientation detector for reporting tothe hand set absolute or relative changes in orientation of the orientedmicrophone and oriented camera. Head set 1122 further includes amicrophone and a speaker located proximate to the mouth and ear of thehuman operator for review of recorded information and for determiningdescriptions of recorded information.

A processor includes any circuitry or subsystem that performs a storedprogram. A processor may include a dedicated digital signal processor, amicrocontroller, a microprocessor, an application specific integratedcircuit, logic circuitry, signal conditioning circuitry, communicationcircuitry, a computer, a radio, a network appliance, combinationsthereof in any quantity suitable for accomplishing one or more storedprograms. For example, processor 1240 includes a digital signalprocessor for digitizing audio signals, a microcontroller for supportingvideo display and user interface controls, a digital signal processorfor supporting an ad hoc transceiver, a network controller forsupporting a wireless link to personal hub 1124, and a microcomputerwith operating system and application software for performing all otherfunctions of hand set 1032. In another implementation, greater signalprocessing throughput is supported with additional parallel processingcircuits and technologies. In another implementation for a differentdata source application, fewer dedicated circuits are used in favor ofone or a few general purpose processing circuits suitable for thethroughput of the different detecting and recording functions of thedifferent data source.

A memory includes any semiconductor, magnetic, or optical technology orcombination for storing information. All or a portion of memory may beon removable media removed from hand set 1032 for transferring data outof hand set 1032 or for introducing data into hand set 1032 (e.g.,software upgrade, addresses for stimulus control, replacementinformation for any information described with reference to FIG. 13).For example, memory 1241, stores information as described with referenceto FIG. 13 using non-removable semiconductor technology. A portion ofmemory 1241 is maintained in nonvolatile memory to avoid data loss inthe event of failure or removal of battery power to handset 1032.

A video monitor provides a display. The display may present legends forcontrols of a user interface. The display may present video informationfor review. The display may present video information for determining adescription. A video monitor may include a processor or circuitry forsupporting the display. A video monitor may employ any displaytechnology suitable for the environment where hand set 1032 is used. Forexample, video monitor 1242 includes a conventional LCD display thatpresents video in shades of green for visibility outdoors. In analternate implementation, video monitor 1242 is included in head set1122 and the correlation of legends on the display with controls of theuser interface does not require the trained user to view his or herhands when operating the controls.

A control, according to various aspects of the present invention, is apart of a user interface that provides input to a processor in responseto an action by an operator. A control may be operated as a consequenceof any muscle contraction by the operator. A control may be incorporatedinto clothing worn by the operator (e.g., gloves, sleeves, shoes). Acontrol may provide analog or binary information to a processor. Acontrol may comprise a detector of a binary condition or a detector ofan analog condition. A control may include a pointer control. A pointercontrol provides to the processor an indication of the operator's intentto have a pointer that is superimposed on a presentation of the displaymove in a particular direction to another point of the presentation. Thepointer may be any symbol or icon. Directions may including up, down,left, and right. Directions may further include arbitrary bearings fromthe current pointer position. A pointer control may further provide tothe processor a binary indication of the operator's intent to have theprocessor “accept” or act with reference to that portion of thepresentation that the pointer currently identifies. For example,controls 1243 include a first plurality of multipurpose binary switchesarranged along an edge of the display of video monitor 1242 and aconventional pointer control providing to the processor directionsincluding up, down, left, right, and “accept”. The switches of controls1243 are sized and positioned on hand set 1032 for operation by theoperator's fingers and/or thumbs. The switches of controls 1243 are alsopositioned to correlate with legends presented on the display of videomonitor 1242. Consequently, the functions of the plurality of switchesmay be defined and redefined by the processor within any suitableoperating context, state, or mode of operation. Controls 1243 mayfurther include dedicated switches (e.g., a switch indicating a time ofinterest during recording, a switch operated to control the stimulus ofany weapon, a switch to toggle recording on/off for author-operatorprivacy) and dedicated analog controls (e.g. display brightness, audioplayback volume).

An ad hoc transceiver supports communication by a candidate for or amember of an ad hoc network. Any suitable communication technologies maybe combined to implement an ad hoc transceiver limited to accomplishreliable performance in the presence of sources of noise and an expectednumber of candidates and members of the ad hoc network. Transmitting bycandidates may be subject to garbling due to simultaneous transmissionson the same channel. Coordination of the transmissions of members may beaccomplished using any suitable conventional protocol and/or channelassignment technique. An ad hoc transceiver may use any suitable securecommunication technology. For example, ad hoc transceiver 1244 providesrelatively short range (less than 5000 meters) communication atrelatively low power (e.g., less than one milliwatt) in frequencychannels between 700 and 1200 MHz. Transmissions by members employspread spectrum techniques.

An audio in circuit provides audio information to a processor in asuitable signal format. Signal conditioning, analog to digitalconversion, sampling, multiplexing, and/or filtering may be accomplishedby an audio in circuit. For example, audio in circuit 1245 provides toprocessor 1240 audio information responsive to analog microphonesincluding hub mike 1224, receiver 1214, head mike 1234, and orientedmike 1235. Conversion to MPEG-4 format may be accomplished by processor1240 and/or audio in circuit 1245.

An audio out circuit provides audio information from a processor in asignal format suitable for communication and/or for conversion intosound. For example, audio out circuit 1246 in cooperation with processor1240 converts audio information from MPEG-4 format to analog format foruse by a conventional speaker (e.g., a head phone speaker). In anotherimplementation, audio in circuit 1245, processor 1240, and audio outcircuit 1246 cooperate to provide audio output for use with conventionalnoise cancellation technologies implemented at hub speaker 1226 and orhead speaker 1236. For example, additional microphones are co-locatednear speakers to provide additional signals to audio in circuit 1245)and processor 1240 includes noise cancellation processing circuitryand/or software.

A local link transceiver provides point to point communication to oneother local link transceiver. A local link transceiver may includemultiplexing and demultiplexing for the communication of information ofseveral formats. A local link transceiver may use any suitable securecommunication technology. For example local link transceivers 1247 and1232 cooperate to replace a wired interface between personal hub 1124and hand set 1032 with a secure wireless interface.

A transceiver includes a transmitter and a receiver. When thetransmitter and receiver share one communication channel, thetransmitter and receiver cooperate to use one antenna. A transceiver mayuse any number of channels in sequence (e.g., for spread spectrumcommunication) or simultaneously (e.g., for acting as a network nodeperforming repeating and routing functions for all messages receivedwhether or not addressed for local processing). Transceivers 1244, 1247,and 1232 include transmitters and receivers. Transmitter 1212 respondsto push-to-talk circuit 1222 of personal hub 1124 and transmitsinformation in response to mixer 1228. Receiver 1214 provides audioinformation to mixer 1230.

As used herein, a signal conveys information. When a functional block isresponsive to information, the circuitry implementing the functionalblock receives a signal that conveys the information and demodulates orotherwise determines the information to perform the function of theblock. Receiving may be continuous or discontinuous. Performing thefunction may occur whenever sufficient information is received.

Components (e.g., hand set 1032, personal hub 1124, head set 1122) of aprimary subsystem (e.g., 1108) may each include respective deviceidentification functions. A device identification function may beimplemented in any conventional manner to identify the component orprimary subsystem to a shift hub as discussed above. The identificationmay be human readable as well as machine readable. If the componentincludes a user interface, the device identification may be entered oredited by the operator.

A push-to-talk circuit provides a transmit enable signal to atransmitter. A push-to-talk circuit may include a user interface with aconventional push to talk switch. An operator actuates the push to talkswitch to begin transmitting. For example, push to talk circuit 1222includes a manual binary switch sized and positioned to be operated byone of the author-operator's thumbs. In another implementation, aconventional voice operated switch (VOX) replaces or cooperates with apush to talk switch.

Hub microphone 1224 and hub speaker 1226 pick up the operator's voiceand play audio into the operator's ear. Hub microphone 1234 provides ananalog signal conveying audio information to mixer 1228 and to locallink transceiver 1232. Hub speaker 1226 makes audible sound in responseto a signal received from mixer 1230. Hub microphone 1224 and hubspeaker 1226 provide redundant functions with head microphone 1234 andhead speaker 1236.

Mixer 1228 receives audio information from hub mike 1224, head mike1234, and oriented mike 1235. In suitable relative volumes among theseaudio sources and at suitable times based on priority of audio sources,mixer 1228 provides audio information to transmitter 1212.

Mixer 1230 receives audio information from receiver 1214 and audio outcircuit 1246 via local link transceivers 1247 and 1232. In suitablerelative volumes among these audio sources and at suitable times basedon priority of audio sources, mixer 1230 provides audio information tohub speaker 1226.

Head microphone 1234 and head speaker 1236 pick up the operator's voiceand play audio into the operator's ear. Head microphone 1234 provides ananalog signal conveying audio information to mixer 1228 and to locallink transceiver 1232. Head speaker 1236 makes audible sound in responseto a signal received from mixer 1230. Due to the location on theoperator's head, head microphone 1234 and head speaker 1236 provide moreprivate audio communication with the operator than possible from hubmicrophone 1224 and hub speaker 1226.

An oriented microphone is moved by the author-operator to receive soundthat approaches the operator's face. An oriented camera is moved by theauthor-operator to capture radiant energy (e.g., ambient or illuminationof visible or IR light) that approaches the operator's face.Consequently, as an author-operator performs his or her routine, audioand video information are captured for recording. Oriented mike 1246 mayhave a relatively narrow field of sensitivity projected in front of theauthor-operator suitable for capturing speech intended for theauthor-operator to hear and respond to. Oriented camera 1248 may have arelatively wide field of sensitivity to correspond more closely with thefield of view of a human author-operator. Oriented microphone 1246 maybe implemented as an omnidirectional microphone or stereo microphone andas such may not be “oriented” in the same manner that oriented camera1248 is oriented.

An orientation detector provides information regarding the orientationof oriented camera 1237. An orientation detector may further provideinformation regarding the orientation of oriented microphone 1235. Anorientation detector may further provide information as to position ofthe author-operator (e.g., longitude and latitude coordinates from aglobal positioning system (GPS) receiver). In other implementations,information as to position is determined for processor 1264 by thelocation of a GPS receiver (not shown) in on-duty transceiver 1128,personal hub 1124, or hand set 1032. Information regarding position andorientation includes azimuth (e.g., cardinal direction toward which theauthor-operator is facing) and elevation (e.g., whether theauthor-operator is facing perpendicular to gravity, looking up to anextent, or looking down to an extent).

Memory 1241 includes data stored in any suitable organization andformat. Contents of memory 1241 in one implementation includes datastructures 1300 as described below with reference to FIG. 13. Data maybe organized for storage in a data structure of any conventional typeincluding value, list, table of records, file, tree, graph, hierarchy ofrecords, or hierarchy of tagged strings consistent with a markuplanguage. Data in any organization and plural organizations may bestored in containers. The description of memory 1241 shown in FIG. 13 ismore akin to a functional block description than a data structure orcontainer description. Nonetheless, the data stored in memory 1241 andthe manner in which it is accessible by processor 1240 specifies thestructure of memory 1241.

Data structures 1300 include program code 1302, local logs 1304,environment logs 1306, audio hub mike streams 1308, audio head mikestreams 1310, audio oriented mike streams 1312, audio on-duty receiverstreams 1314, video oriented camera streams 1316, scene descriptiondocuments 1318, scene description audio streams 1320, scene descriptionvideo streams 1322, menus 424, interactive voice response streams 426,data collection forms 428, data collection graphics 430, and other data432.

Program code 1302 includes instructions performed by processor 1264 toaccomplish any methods and functions ascribed to processor 1240 or handset 1032. Program code 1302 includes operating systems for processor1264 and application software. Application software includes softwarefor recording audio and video in MPEG-4 format, software for operating auser interface for the hand set as discussed herein, software for reviewof recorded information, software for determining revisions in MPEG-4format, and software for communications. For improved evidence gatheringand transfer, application software may further include software fornoise cancellation, determination of position of the incident recorder(e.g., global position), identification of the author-operator of thecamera (during recording) and the handset (during revising),identification of other parts of the incident recorder (e.g., serialnumbers, types, manufacturers), interactive voice response,transcription of speech to text, and 3D modeling for graphicpresentations including data collection graphics.

Recorded audio and video may be stored for at least two purposes. Apre-movie buffer may retain continuously recorded audio and videoinformation in a circular buffer (e.g., 60 seconds duration) so thatwhen the operator indicates a time to begin recording a movie (e.g.,operation of a control 1243), audio and video from before the operator'sindicated time is available, for example, to help explain why the userdecided to begin recording the movie. Any number of movies may berecorded, preferably one movie at a time. The end of each movie may beindicated by the operator by operation of any control 1243 or bycooperation with interactive voice response after lapse of a period oftime. Controls 1243 may include a dedicated switch for indicating an endof a movie. Menus may permit the user to actuate a general purposeswitch to indicate the end of a movie. An incident report may consist ofa revised movie. An incident report may comprise a revised movietogether with portions of logs, interactive voice response streams, datacollection forms or overlays, data collection graphics or overlayswhether or not any or all of this information is included in a revisedmovie. In a preferred implementation, a revised movie includes allrelevant information including one or more movies, all scenedescriptions, portions of logs, interactive voice response streams, datacollection forms or overlays, and data collection graphics or overlays.

Storage of recorded audio or video in a “buffer” as stated herein doesnot designate a format for storage. In other words, a buffer as usedherein may hold any audio or video stream in any format (e.g., an MPEG-4format). A pre-movie or movie stored in a buffer does not designate acontiguous region of memory. Streams that are part of a pre-movie may bestored in the same or different buffers. Streams that are part of amovie may be stored in the same or different buffers. Streams that arepart of a description or of a revised movie may be stored in the same ordifferent buffers. In one implementation a buffer is coextensive with anMPEG-4 container.

A log is a list of records each describing a change and noting the timewhen the change occurred. Local logs 1304 are updated on the occurrenceof a change in the configuration or operation of incident recorder 1108and hand set 1032. For example, local logs 1304 may include an entry forapplication of power to hand set 1032, removal of power from hand set1032, adjustment of a time base used by hand set 1032 (e.g.synchronization of time of day, date), entry and exit from privacy mode(e.g., no recording of audio or video for pre-movie, movie, orrevision), and adjusting or establishing parameters that affectrecording or revising (e.g., pre-movie buffer length, video resolutionfor pre-movie and/or movie, IVR script changes, software upgrades).

Environment logs 1306 are updated on the occurrence of a change in theenvironment where incident recorder 1108 is being used. For example,environment logs 1306 may be updated in response to notice of acandidate beacon message received, a message indicating the incidentrecorder is part of an ad hoc network, notice of change in membership orsubstantial change of GPS location of members of an ad hoc network,identification of a weapon proximate to the incident recorder 1108,notice of change in the identity of the author-operator, weaponactivation message sent (what address or group address was sent),stimulus control message sent (intended type of electronic controldevice, control information sent, address or group address it was sentto), directive received for coordinated evidence collection (from whattype and identity of device, what directive required of this incidentrecorder or operator), and notice that reorientation in accordance witha directive was accomplished.

Audio hub mike streams 1308 include buffers for storage of audio for anyone or more of pre-movies, movies, scene descriptions, interactive voiceresponse answers by the operator, and revised movies.

Audio head mike streams 1310 include buffers for storage of audio forany one or more of pre-movies, movies, scene descriptions, interactivevoice response answers by the operator, and revised movies.

Audio oriented mike streams 1312 include buffers for storage of audiofor any one or more of pre-movies, movies, and revised movies.

Audio on-duty receiver streams 1314 include buffers for storage of audiofor any one or more of pre-movies, movies, and revised movies.

Video oriented camera streams 1316 include buffers for storage of videofor any one or more of pre-movies, movies, and revised movies.

Scene description documents 1318 include buffers for text entry orscanned paperwork for revisions and revised movies.

Scene description audio streams 1320 include buffers for supplementalaudio from the author-operator (spoken impromptu or in reply to aninteractive voice response script) for revisions and revised movies.

Scene description video streams 1322 include buffers for supplementalvideo for revisions and revised movies.

Menus 1324 include legends as described below with reference to Table 1.

Interactive voice response (IVR) streams 1326 include audio streams usedto prompt the author-operator and streams used to recognize the spokenreply of the author-operator to an IVR prompt.

Data collection forms 1328 include blank forms and filled in forms.Forms include parameter names and storage for the selected value if aselection list of values is part of the form and/or storage for freeform values (e.g., audio streams, video streams, transcribed text, textfrom speech recognition or IVR functions).

Data collection graphics 1330 include blank graphics and markedgraphics. Marks may be indicated by operation of any of controls 1270(e.g., a pointer control) and/or audio streams (e.g., spoken impromptuor in reply to an interactive voice response script).

Data 1332 includes all variables and temporary storage required for theperformance of the program code 1302. Data may further include deviceidentification for the component that stores the data structure (e.g.,hand set 1032) and/or for the primary subsystem to which it is a part(e.g., 1108) and/or any or all of its components (e.g., personal hub1124, head set 1122, on-duty transceiver 1128).

A hand set includes any device that facilitates the review anddescription of recorded audio and/or video. For example, hand set 1032of FIGS. 10, 11, 12A, and 14 may be implemented as shown in a frontview, FIG. 14. As shown, the top side, right side, and bottom side areblank. The rear side includes terminals for connecting a battery chargerof shift hub 1020 to the battery that is internal to hand set 1032.Antennas for the ad hoc transceiver and the local link transceiver arenot shown. Hand set 1032, as shown, includes both dedicated controls(1432, 1434, and 1436) and general purpose controls (1404, and 1408).The general purpose controls are adjacent a display. All controls aresized an positioned for operation by the author-operator's fingers orthumbs. For example, when hand set 1032 is attached to personal hub 1124(FIG. 11), only controls 1432, 1434, and 1436 are accessible andoperated by the operator's fingers. When hand set 1032 is removed frompersonal hub 1124, all controls are accessible, sized, and positioned tobe operated by the operator's thumbs. The operator's fingers are used tohold and maintain the hand set generally between the operator's palms.

User interface 1400, shows by way of example, a front view of hand set1032 including an enclosure 1402, display 1406, a column of buttons 1404along one edge of display 1406, a pointer control 1408, a stimuluscontrol button 1432, a mark button 1434, and a privacy button 1436.Display 1406 is shown providing a presentation of legends 1412, apresentation of data collection graphics 1422, and a presentation oforiginal video 1424 in a picture-in-picture (PIP) format of a scenepresently being described by the author-operator.

Enclosure 1402 comprises high impact plastic. Enclosure 1402 may bewater resistant to protect all functions of hand set 1032 from damageduring rainy weather or accidental submersion. Enclosure 1402 may bewater resistant for incident recording under water.

Display 1406 is part of video monitor, discussed above.

The column of buttons 1404 along one edge of display 1406 providescontrols for a multi-purpose user interface. Each legend 1412 (fivelegends shown) describes the present function for the respective button.Legends may be organized in hierarchical menus.

Pointer control 1408 facilitates entry of cursor directions up, down,right, and left. A center “accept” function is also provided. Thepointer control may rock slightly about its center in a conventionalmanner.

A stimulus control button 1432 allows the operator to initiate or modifya stimulus control function of an electronic control device (or anyfunction of a suitable data source or weapon) that is addressable andwithin communication range (e.g., within range of ad hoc transceiver).

When recording a pre-movie, operation of mark button 1434 allows theoperator to begin recording a movie. The resolution of audio and/orvideo recording may be changed to correspond to the configuration formovie recording (e.g., preferably a higher resolution than pre-movierecording). When recording a movie, operation of mark button 1424designates a time (e.g., the present time of day) as a time when adescription may be added upon review of the movie. During recording,hand set 1032 may log the operation of button 1434 (e.g., in a generalor special purpose log of local logs 1304). Each operation of button1434 during recording a movie is herein referred to as making a mark,recording a mark, or designating a scene for review or description.During review of a movie, a list of logged times when button 1434 wasactuated may be used (e.g., in a manner analogous to hypertext links) toquickly navigate to respective scenes. The log may also track whether ornot a description has been made for each recorded mark. During review ofa movie, a list of recorded marks without descriptions may be presentedto assist in completing a revision. During review of a movie, a list ofrecorded marks with descriptions may be presented to assist in reviewingdescriptions.

A privacy button 1436 stops audio and video recording. When actuated bythe user during pre-movie recording, actuation stops pre-movierecording. When actuated during movie recording, actuation stops movieand pre-movie recording.

The picture-in-picture format may be used to review and combination oftwo video streams of the same or different types discussed withreference to FIG. 13. As shown in FIG. 14, a scene (1424) is beingdescribed by entries of cursor locations on a data collection graphic1422. Data collection graphic 1422 portrays a human front view forcollecting a description of where on the suspect (1102) the electronicweapon's tethered darts made impact (1112, and 1114). Although thisinformation may be clearly visible from the video, making an entry on aform may facilitate statistical analysis. The author-operator mayoperate pointer control 1408 to locate the cursor over a point ofgraphic 1422 that corresponds to a contact point (e.g., 1112) andactuate the “accept” function of pointer control 1408, as discussedabove. The author-operator may repeat this step for the second contactpoint (e.g., 1114). Completion of data collection with reference tographic 1422 may be indicated by operator actuation of a suitable button1404 in accordance with its legend (see menus discussed below withreference to Table 1).

FIG. 15 is a state change diagram of states that define a user interfacein an implementation of hand set 1032 of FIGS. 10, 11, 12 and 14. Statesinclude setting state 1502, recording state 1504, playing state 1506,describing state 1508, audio/video entry state 1510, graphics entrystate 1514, and interactive voice response state 1516. Operationcontinues in a state until all conditions are met for a state change.Table 1 describes legends and a next state entered after operation of aswitch corresponding to a legend. The numbered legends in Table 1correspond to the column of switches 1404 of FIG. 14 numbered from topto bottom. Not all switches are used in each state.

TABLE 1 State Legends Next State Setting 1 Record 1 Recording 2 Play 2Playing 3 Device 3 Setting 4 Personal 4 Setting 5 Agency 5 SettingRecording 1 Privacy Toggle 1 Setting 2 Monitor Toggle 2 Recording 3Setting 3 Setting Playing 1 Rate/Skip 1 Playing 2 Raw/Described 2Playing 3 Mark 3 Describing 4 Setting 4 Setting Describing 1 Add Graphic1 Graphic Entry 2 Add Audio/Video 2 Audio/Video Entry 3 Add IVR 3 IVR 4Play 4 Playing Graphics Entry N/A Describing Audio/Video N/A DescribingEntry IVR N/A Describing

Table 2 describes the functions of the pointer control 1408 in eachstate. In Recording state 1504, the pointer control has no functionsunless recording is being monitored. In Playing state 1506, thefunctions of the pointer control depend on whether a movie is beingplayed without descriptions (raw) or with descriptions (described).

TABLE 2 State Pointer Control Functions Setting ↑ Highlight parameterrow above present row ↓ Highlight parameter row below present row →Highlight alternative right of present, or scroll to increasing values ←Highlight alternative left of present, or scroll to decreasing values ●Accept newly specified entry Recording If monitoring on the display oflive recording is enabled: ↑ Increase brightness of display ↓ Decreasebrightness of display → Increase volume ← monitor decrease volume ● n/aPlaying Rate Skip ↑ Faster First Mark ↓ Slower Last Mark → Forward NextMark ← Reverse Previous Mark ● Pause Toggle Pause Toggle Describing N/AGraphic Entry ↑ Move cursor up ↓ Move cursor down → Move cursor right ←Move cursor left ● Accept Position Audio/Video N/A Entry IVR N/A

All states are available when the hand set is removed from personal hub1124. Operation begins in Setting state 1502 when power is initiallyapplied to hand set 1032. Unless not permitted by the Privacy function,pre-movie recording begins or continues in Setting state 1502 whether ornot hand set 1032 is attached to personal hub 1124. In response tooperation of mark button 1432, pre-movie recording is stopped and movierecording is started. Depending on memory size and intended use of handset 1032, recording of a movie preferably continues for several hours(e.g., 4 hours). During movie recording, marks are recorded to simplifylater making revisions. After movie recording is stopped, review andrevisions may be made.

In Setting state 1502, 5 legends identify 5 submenus for setting theconfiguration of hand set 1032. See Table 3 for a description of thesubmenus that apply in the settings state. In each submenu, apresentation of a list of parameters is displayed. A parameter to set islisted on a row of the display. The current setting for alternativevalues may be highlighted; and the current value for numeric and datevalues may be shown. For a new alternative value, the desiredalternative may be highlighted and “accepted” by operation of pointercontrol 1408 as described for Setting state 1502 in Table 2. For a newnumeric or date value, pointer control 1408 may be used to “scroll” toan appropriate value. An IVR script may be used to specify a desiredvalue. The IVR script may be accompanied a presentation of writtenalternatives. After specification of a value for a Setting submenu ofTable 3, the Setting main menu of Table 1 is again presented.

TABLE 3 Setting State Submenu Parameter Alternative Values Record ModeA/V, V Only, A Only, Privacy Resolution Limited, Full Monitor A/V, VOnly, A Only, None Playback Date Jan. 1, 2008 Time 21:35:02 Content Raw,Described Device Volume 4 Brightness 5 Ad Hoc Channel A, B, C, D, E AdHoc Power Off, Limited, Full Roles Lead only, Lead and Follow, Followonly, None Personal Name (Agency List) Voice Sample Jan 30, 2008, NewPhoto Sample Jan 30, 2008, New Agency Movie duration Full Shift, LimitedShift Pre-movie Video & Audio, Video Only Stimulus Ctrl1 Group-Address1Stimulus Ctrl2 Unit-Address1 Stimulus Devices Projectiles, Cuffs,Clothing

In the Record submenu, recording can be audio and video, or limited tovideo only, or audio only. Video resolution may be set to a standardresolution (full) or a prescribed lower resolution (limited) forconserving memory in hand set 1032. Display 1406 may be activelymonitoring the oriented camera or blank. Audio output may monitor theoriented microphone or be silent.

In the Playback submenu, content of the playback may be selected as theoriginal movie (raw) or the latest revised movie (described). During theplayback of a revised movie, playback stops at each recorded mark andthe description, if any, is played. When playback of the description isfinished, the movie plays until the next recorded mark. During playbackaudio information is composed to produce sound on head speaker 1244 andhub speaker 1226 while video information is composed to produce apresentation on display 1406.

In the Device submenu, channels and power level for communication (viaad hoc transceiver) may be specified. Hand set 1032 may be authorized toaccept and delegate support tasks (lead), accept support tasks (follow),or neither accept nor delegate support tasks. Support tasks may relateto tactics (e.g., act as an actuator for stimulus control),communication (e.g., serve as ad hoc network node with routingcapability), and/or evidence (e.g., directives to reorient the orientedmicrophone or oriented camera for additional evidence gathering for anincident in process or prior to an action regarding an incident).

In the Personal submenu, audio and video recordings made byauthor-operator of himself or herself may be made. To avoid text entryerrors, the correct spelling of all possible users names may be providedas a list from which the operator selects his or her own name.

In the Agency submenu, the amount of recording may be limited to lessthan an 8 hour period as desired. By limiting the recording, additionalmemory may be available for descriptions and revisions. Pre-movierecording may omit audio recording. For tactical tasks (e.g., stimuluscontrol), addresses may be specified as unit addresses (e.g., a list orrange or list of ranges) used for example for reactivating a singleround electrified projectile. Further, addresses may be specified asgroup addresses used for example for reactivating any round having anaddress within the group.

An electronic control device (e.g., an electrified projectile) may haveany number of addresses for particular stimulus control functions. Forexample, an electrified projectile may have only one stimulus controlfunction, that is to reactivate the stimulus to restrain the suspectafter an initial stimulus duration has lapsed. Other stimulus controlfunctions may include specifying any parameter of the stimulus signal(e.g., charge per pulse, pulse repetition rate, pulses per pulse group,pulse duration, energy available per pulse, pulse amplitude). Forexample, a single round electrified projectile may have a group address(e.g., 1010) and a unit address e.g., (265). The group address may beapplied to all projectiles used by a particular agency. The unit addressmay fall within the definition of a group address when the group addressis understood to indicate a range (e.g., group address 200 includes allunit addresses between 201 and 299, including 265).

In Recording state 1504, pre-movie recording stops and movie recordingbegins. The transition from setting state 1502 to recording state 1504may be accomplished by operation of a dedicated control (e.g., 1434). Inone implementation, exit from recording state 1504 to return to settingstate 1502 is responsive to the operator holding a dedicated control forat least a minimum duration (e.g., 1434 for 3 seconds). In Recordingstate 1504 the display may be active, static, or blank. If the Privacyfunction is active, display 1406 presents a static banner (e.g.,“Privacy”). If the Privacy function is not active and the Monitoringfunction is active, then display 1406 presents a live video orientedcamera stream 1316. If the Privacy function is not active and theMonitoring function is not active, display 1406 is blank.

In Recording state 1504, the Privacy Toggle functions like the privacybutton 1436. The Monitor Toggle function may be used to activate thedisplay and at least one speaker for a live presentation of the moviebeing recorded.

Prior to transition to playing state 1506, a presentation of a list ofmovies and revised movies (e.g., identified by start time and date) maybe offered to the operator for selection. The list and its controls maybe similar to parameters listed in Setting mode 1502, as described withreference to Table 2. While in Playing state 1506, a transition toDescribing state 1508 may be made by operation of Mark button 1434. TheRate/Skip function allows operator control of playback speed anddirection using pointer control 1408 with one of two sets ofcapabilities. In Skip mode, control of playback using pointer control1408 refers to recorded marks. In Rate mode, control of playback doesnot refer to recorded marks. The Raw/Described function specifieswhether the playback ignores descriptions (raw mode) or stops at eachrecorded mark and plays the description (descripted mode). When playingwith descriptions, the presentation on display 1406 may include athumbnail of the scene being described in a picture-in-picture formatwhile playing the description. Other information along the top andbottom edges of the display may include any of the following: location(e.g., GPS) of the incident recorder when the recording was made,orientation described by the orientation detector 350 (e.g., azimuth andelevation), whether a description is available for the scene beingplayed (e.g., only in raw mode), the date and time of day when therecording was made or when the description was made, the time of thepresently playing scene with reference to duration of the entire movieor revised movie. During a playback (raw or described) the Mark functionallows the operator to immediately transition to Describing state 1508to enter a new description whether or not a recorded mark exists at thistime in the movie.

In Describing state 1508, a recorded mark is made in association withthe present scene identified for description. Three functions areavailable for adding three types of descriptions: graphics, audio and/orvideo recording, and a guided discussion involving an Interactive VoiceResponse script. During entry of a description, a thumbnail of the scenebeing described may be shown on the display in a picture-in-pictureformat. The Add Graphic function transitions to Graphics Entry state1514 where, after selection of a suitable data collection graphic 430,the author-operator may mark the graphic form and add it to the revisedmovie in association with the recorded mark or identified scene. The AddAudio/Video function transitions to Audio/Video Entry state 1510 whererecording from oriented camera and head microphone begins immediately.The recorded information is added to the revised movie in associationwith the recorded mark or identified to the scene. The Add IVR functiontransitions to IVR state 1516 where an IVR script is begun to gatheraudio information from the author-operator. A PIP presentation may inaddition present written prompts during the IVR script.

Legends may be presented beside the movie or PIP presentation. Inanother implementation, the entire display area is used for the movie orPIP presentation.

An incident recorder, according to various aspects of the presentinvention, may periodically transmit its unique communication addressand its location (e.g., GPS coordinates). For example, when an incidentrecorder as discussed above is configured to Lead it responds to otherincident recorders that have locations proximate to a location ofinterest. A location of interest may be a location of an electroniccontrol device (e.g., 1270) that is subject to addressable stimuluscontrol. A location of interest may be a location of a human or animal(herein called a target) (e.g., 1610) planned to be hit by such anelectronic control device (e.g., a wireless electrified projectile).

The Lead incident recorder may request any of several support tasks beaccepted by other subsystems configured to Follow. Tactical supporttasks may be requested. Tactical support tasks may include any taskrelated to apprehension of a suspect. Tactical support tasks may includetransmitting a stimulus control signal to an electronic control devicethat is capable of addressable stimulus control. Communication supporttasks may be requested. Communication support tasks may include anytasks for enhancing communication in an ad hoc network (e.g., acceptingnew members into the network, routing traffic to or through nodes of thenetwork, discovering routes, informing other nodes of members andappropriate routes, extending the range of the network). Collectionsupport tasks may be requested. Collection support tasks may include anydirectives for operation of an incident recorder. For example, asking aFollower to turn and record a movie facing the likely location of asuspect. Assistance with gathering evidence may be facilitated.Assistance with stimulus control may be facilitated. Assistance withcommunication among incident recorders may be facilitated.

A subsystem suitable for performing a Follow role as to addressablestimulus control, is herein called an activator. An activator maycomprise a hand set (though memory for software for recording may beomitted with commensurate simplifications of processor and local linktransceiver); a head set (though an oriented mike, oriented camera, andorientation detector may be omitted); a personal hub (though support foromitted functions of the hand set and head set may be omitted); and anon-duty transceiver. These components, except for omitted functions, mayinclude the structures and functions as discussed above. For example,activator 1260 of FIG. 12B includes processor 1261, memory 1262, videomonitor 1263, controls 1264, ad hoc transceiver 1265, and wiredinterface 1266. Processor 1261 is analogous to processor 1240 withcommensurate simplifications due to the reduced set of functions and thespecial functions of an activator as compared to a hand set. Memory 1262may include the data structures 1300 discussed above withsimplifications commensurate with the functions of processor 1261. Videomonitor 1263 and controls 1264 may be simplified in comparison tocounterparts in hand set 1032 when operation with a video camera is notrequired. The menus for the user interface (1263, 1264) of an activatormay be simplified in accordance with the functions of processor 1261. Adhoc transceiver 1265 is compatible with ad hoc communications discussedabove with shift hub 1020, handset 1032 and ECD 1270. Wired interface1266 facilitates docking in docks 1026 but may be omitted when ad hoctransceiver 1265 performs necessary configuration (e.g., addresses) anddata transfer functions (e.g., logs).

An electronic control device includes any apparatus having a circuit forelectrical stimulation as discussed above. A primary subsystem mayconsist of an ECD. An ECD may be packaged as a hand gun (launchingprojectiles as in FIG. 11), stun baton, or wireless electrifiedprojectile (propelled from a launcher as in FIG. 16). One or more ECDcircuits may be packaged as a mine, grenade, check-point turret, or anarea denial installation. One or more ECD circuits may be incorporatedinto clothing, hand cuffs, shackles, shields, or nets. For example, ECD1270 of FIG. 12C includes processor 1271, memory 1272, transceiver 1273,stimulus generator 1274, deployment unit 1275, and wired interface 1276.These functions are described in the US patents incorporated herein byreference.

Transceiver 1273 is a reduced capability transceiver when all thefunctions of an ad hoc transceiver are not required. Transceiver 1273may be replaced by a receiver when no transmit functions are desired.

Wired interface 1276 may be omitted when not required for writing anaddress into the ECD and recharging an internal battery.

Deployment unit 1275 may deploy probes (as in ECD 1110 or as inprojectile electrode deployment). Deployment unit 1275 may propel wiretethered probes (not shown) from the ECD (e.g., ECD is a launcher), ordeploy electrodes (not shown) into position for contacting a target(e.g., ECD itself is a wireless electrified projectile). Deployment unit1275 may be omitted for example if the ECD itself is launched by anexternal propellant toward the target and no further deployment ofelectrodes is needed.

In shift hub 1020, hand set 1032, activator 1260, and ECD 1270, the adhoc transceiver, memory, and processor may cooperate according toapplicable commands of Table 4. Transmitting may include transmitting anaddress for further communication. Transmitting may include transmittingan acknowledgement and/or reply to a command received. Receiving mayinclude receiving and taking suitable action. SS stands for secondarysubsystem and includes shift hubs (SH) (e.g., 1020) and locker docks(LD). PS stands for primary subsystem and includes incident recorders(INR) (e.g., 1108), activators (AVR) (e.g., 1260), and electroniccontrol devices (ECD) (e.g., 1270).

TABLE 4 Sources of Command −> Command description Receivers of Command:: Effect SS, INR −> Begin beacon of identification. Beacon PS :: beginstransmitting its unique timing may be specified. address to be used infurther communication and its location (if available) SS −> Synchronizetime base. Current or future PS :: sets its date and time of day timetime may be specified. base (e.g., used for logs) SS, INR −> Stop beaconof identification. Quiet PS :: transmits no beacon messages period maybe specified. during a default period of the specified period. SS, LD,INR −> Report configuration. PS :: transmits its make, model number,location, identification, and the same for its components; ECD :: mayfurther transmit its capabilities (e.g., loaded, safety off, batterycapacity, number of rounds remaining, number of rounds launched, historyof stimulations) and configuration settings (e.g., electrical stimuluscharge, energy, timing). INR :: may further transmit its capabilities(e.g., storage space available for further recording) and itsorientation. SS, PS −> Change configuration as specified. ECD adjustsany parameter of the stimulation current (e.g., pulse width, pulserepetition rate, amplitude, charge per pulse). AVR −> Controlstimulation. Launch, Start, Stop, ECD :: performs the command and/orRepeat may be commanded. Any immediately but within its capabilities.stimulation circuit parameter or output signal For example, a launchcommand is more parameter may be affected. The parameter to suitable fora launcher than for the affect and the new value may be specified.projectile being launched. If the ECD in Start/Stop/Repeat magnitudesand timing may be addition has a manual trigger, the Start specified.function may enable operation of the electrical stimulation circuit inresponse to a next operation of the trigger (e.g., by an operator or bythe target). SS −> Accept new identification. Deletion of prior PS ::accepts and stores a group address or identification may also becommanded. unique address for use in future receiving and/ortransmitting. SS −> Transfer an incident report. Date and time PS ::transmits its log of events; identifying the report may be specified.INR :: further transmits stored incident information as a created and/orrevised incident report. PS −> New incident identifier. May specifystart PS :: transmits an acknowledgement and time and location of thesuspect. May specify start associates the new incident identifier withtime in the past. May indicate incident has not yet the current or nextincident. started. PS −> Reorient to face new location, elevation. INR:: notifies operator to orient toward May specify azimuth if receiver'slocation is new location (or azimuth) and elevation. known and receivercannot determine new location. May specify time when action must becompleted. PS −> transmit at a particular time for purposes of PS ::transmits at designated time determining distance from commanding PS toenabling time of flight ranging, responding PS (range). triangulationranging when one subsystem is moving with respect to another, and/ortriangulation ranging by two subsystems near an ECD. SS, PS −>Enable/Disable stimulation capability ECD :: for an operator triggeredECD (e.g., hand gun, grenade, area denial system), when enabled, anoperator pulling the trigger will activate a launch projectiles and/orstart of electrical stimulus; for a target triggered ECD (e.g., cuffs,clothing, mine, area denial system), the trigger operated by the targetis effective to launch projectiles and/or start an electrical stimulus.

FIG. 16 is a plan view of another hypothetical incident involving threelaw enforcement officers apprehending a suspect while each officer isoperating a respective primary subsystem of the present invention. Thesesubsystems are being worn by officers at different locations. Subsystem1108 is northwest of subsystem 1260, which is northwest of subsystem1109. Suspect 1610 will be hit by a wireless electrified projectile typeECD 1270 both being northeast of subsystem 1260. An exemplary sequenceof communication among subsystems 1108, 1260, 1109, and projectile 1270is described in FIG. 17.

In incident 1600, incident recorder 1108 is configured to Lead,activator 1260 is configured to Follow. And, incident recorder 1109 isconfigured to Follow. For simplicity of this discussion, the roles Lead,Lead and Follow, and Follow are general as to all authorizations relatedto stimulus control, and all directives as to evidence gathering andcommunication. In another implementation, these roles may be furtherlimited to particular functions in each of the categories of stimuluscontrol, evidence gathering, and communication. Configuration may alsobe expanded to permit several roles of any type to be set for a singleincident recorder as may be suitable for a particular expected security,law enforcement, or military incident.

Communications between incident recorders, activators, and electroniccontrol devices for stimulus control functions may be accomplished withone ad hoc transceiver in each subsystem. In another implementation,different transceivers are used for different communication links. Useof one ad hoc transceiver is appropriate where all communication usesone communication channel and protocol. If greater communicationcapabilities are required by the expected environment in whichcommunication is to be reliable, different channels may be used anddifferent transceivers may be used for each type of device: incidentrecorder, activator, electronic control device.

The sequence 1700 of communications described in FIG. 17 accomplishescommunication support, tactical support, and recording support in anexemplary implementation applied to a hypothetical incident.

At time 1702 activator 1260 of its own initiative transmits its locationand unique address omnidirectionally (e.g., a beacon) or fortuitously inthe direction of incident recorder 1108. For example, activator 1260 maytransmit periodically in a sequence of directions. The period may berandom to reduce interference from other beacon broadcasts. At time 1702incident recorder 1108 receives the transmission from activator 1260. Inanother implementation, activator 1260 further transmits itsconfiguration (e.g., an activator make T, model xyz) according to aknown list of types of systems that communicate for any of the purposesdescribed above.

At time 1704 incident recorder 1108 tests the proximity of activator1260 to a suspect 1610. The location of suspect 1610 was determined byincident recorder 1108 by using a measure of azimuth and range findingas discussed above. The location of activator 1260 is apparent from themessage received from activator 1260. The test passes because thedistance between activator 1260 and suspect 1610 is less than a limit(e.g., closer than incident recorder 1108 is to suspect 1610).

At time 1706 incident recorder 1109 transmits its location, uniqueaddress and may also transmit its configuration in a manner analogous tothe message at time 1702. At time 1706 activator 1260 receives thetransmission from incident recorder 1109.

At time 1708 activator 1260 tests the proximity of itself to incidentrecorder 1109 in a manner analogous to the proximity test at time 1702.The test passes.

At time 1710 incident recorder 1108 transmits a tactical support requestaddressed to activator 1260 that authorizes an addressable stimuluscontrol to be initiated by the operator of activator 1260 for an addressof electronic control device (e.g., the projectile 1270) having areactivate capability and having a matching address. The address for ECD1270 may be a unique address or may be a group address (e.g., all ECDschecked-out to the operator of incident recorder 1108, all ECDsechecked-out to a team, all ECDs checked-out on a particular date, allECDs of a particular configuration). The location of suspect 1610 isincluded with the request. The fact that the projectile has not yet beenlaunched is included with the request.

At time 1712 incident recorder 1108 transmits a recording supportrequest that asks for assistance for gathering evidence. The request isaddressed to activator 1260. Both requests at time 1710 and time 1712may be accompanied by information for activator 1260 to determinewhether accepting these tasks is within its available resources.

At time 1714 activator 1260 transmits an acceptance of the delegatedtactical task received at time 1710.

At time 1716 activator 1260 notifies its operator that he or she isauthorized to reactivate a stimulus function for a projectile at thelocation of the suspect 1610. The notice includes the fact ofauthorization implied from the receipt of a valid address for activator1260. The notice further includes identification of a particular type ofstimulus control (reactivation) for a particular type of electroniccontrol device (projectile) derived from the request. The notice stillfurther includes the azimuth to the projectile derived from the positionof the projectile provided in the request. The operator now knows that auser interface control (e.g., button 1432) is enabled to perform thereactivation whenever he or she deems reactivation is necessary. Thenotice may be made by synthesized voice delivered to a speaker (e.g.,head speaker 1244) or by a presentation on a display (e.g., 1406)accompanied by an alert to review the display for a message.

At time 1718 activator 1260 transmits a recording support requestaddressed to incident recorder 1109 that asks for a reorientation of theincident recorder toward location 1610.

At time 1720 incident recorder 1109 transmits an acceptance of therecording support task. The transmission is addressed to activator 1260.

At time 1722 incident recorder 1109 notifies its operator to be ready toturn his or her oriented microphone and oriented camera. In anotherimplementation, the operator of incident recorder 1109 is notified andmust approve the request before the task is accepted.

At time 1724 activator 1260 transmits an acceptance of the recordingsupport task. The transmission is addressed to incident recorder 1108.

At time 1726 incident recorder 1108 addresses a transmission toactivator 1260 with information intended for incident recorder 1109 withrespect to the recording support task at time 1712. Incident recorder1109 may be out of range from incident recorder 1108.

At time 1728, in response, activator 1260 addresses a transmission toincident recorder 1109 and transmits (e.g., forwards) a copy of theinformation activator 1260 just received. By forwarding the information,activator 1260 is performing a communication support task. Othercommunication support tasks (e.g., to become a master of the network forpurposes of creating and managing a routing table for supporting centralreview of multiple video streams) may be requested, evaluated as tosufficiency of resources to accomplish the task, and accepted usingsimilar request/accept communications not shown. On receiving theforwarded information, incident recorder 1109 notifies its operator toreorient according to the forwarded information, that is toward location1610. An audible and/or visible indication of the present orientationerror measured between present orientation and desired orientation maybe generated (e.g., by the parts of incident recorder 1109 correspondingto orientation detector 1238, transceivers 1232, 1247, processor 1240,audio out circuit 1246, mixer 1230 and head speaker 1236) and continueduntil null. The audible and/or visible indication of error may vary(e.g., pitch, pulse rate, color, brightness) with efforts to reorientuntil proper orientation is achieved.

At time 1730 the operator of incident recorder 1108 also operates alauncher that launches ECD 1270 (a wireless electrified projectile)toward target 1610. Projectile 1270 hits target 1610 and begins a30-second cycle that includes electrical stimulation that interfereswith the skeletal muscles of target 1610. Target 1610's ambulation isstopped because all skeletal muscles in his or her legs contractcontinuously for the 30-second cycle. Incident recorder 1108 may alsoaddress a transmission to activator 1260 with information supporting thetactical task that was delegated and accepted. This message may beomitted if all necessary information was already transmitted with therequest.

At time 1732 the operator of activator 1260 decides, according to his orher training and judgment, to reactivate the electrical stimulusgenerating function of ECD 1270. Reactivating may provide the operatorof activator 1260 sufficient time to arrive at the suspect's locationand complete an arrest (e.g., place hand cuffs (not shown) on thesuspect). This operator actuates a control 1264 of the user interface ofactivator 1260 (e.g., analogous to button 1432 of hand set 1032). Inresponse to actuation, activator 1260 addresses a transmission to ECD1270 and transmits a stimulus control command.

At time 1732, ECD 1270 reactivates its signal generator 1274. The effectof reactivating may extend the 30-second cycle for an additional 30seconds (e.g., stretch it up to 59 seconds), or schedule a break betweencycles (e.g., 3 seconds) and then perform a second 30-second cyclesimilar in all respects to the first 30-second cycle. In anotherimplementation, reactivation results in an adjusted electrical stimuluscurrent that may be in accordance with information transmitted fromincident recorder 1108 at time 1730.

The following patents and patent applications are incorporated herein bythis reference in their entirety for any purpose without being limitedby the context of this statement.

TABLE 5 Patent or Patent Application Title Status Ser. No. Less LethalWeapons and Methods Issued 10/673,901 for Halting Locomotion Systems andMethods for Immobilizing Issued 10/364,164 Using Plural Energy StoresSystems And Methods For Managing Issued 10/447,447 Battery Power In AnElectronic Disabling Device . . . Systems And Methods Using An Issued10/714,572 Electrified Projectile Systems and Methods For Signal Issued10/949,828 Generation Using Limited Power Systems and Methods for Issued10/957,315 Illuminating a Spark Gap in an Electric Discharge WeaponSystems And Methods for Issued 10/750,374 Immobilization Systems andMethods for Issued 10/750,551 Immobilization Using Selected ElectrodesElectric Discharge Weapon Issued 10/893,467 Safe And EfficientElectrically Issued 10/631,683 Based Intentional Incapacitation DeviceComprising . . . Electrical Weapon Having Controller Issued 11/164,710for Timed Current Through Target and Date/Tine Recording Less LethalWeapons for Multiple Shots Issued 11/164,764 Systems and Methods forElectronic Issued 11/270,989 Weaponry Having Audio and/or VideoRecording . . . Systems and Methods for Target Impact Issued 11/457,046Handheld Stun Gun for Incapacitating Issued 10/016,082 A Human TargetSystems And Methods For Incapacitation Issued 10/971,983 UsingBiofeedback Dual Operating Mode Electronic Allowed 11/457,549 DisablingDevice Systems and Methods having a Power Pending 10/892,083 Supply inPlace of a Round of Ammunition Systems and Methods for ElectronicPending 11/530,996 Weaponry with Deployment Unit Detection. Systems andMethods for Modular Pending 11/428,760 Electronic Weaponry Systems AndMethods For A User Pending 11/428,892 Interface For Electronic WeaponrySystems and Methods for Propelling Pending 11/428,801 an ElectrodeSystems and Methods for Local and Pending 11/307,408 Remote StunFunctions in Electronic Weaponry. Systems And Methods For ActivatingPending 11/307,569 A Propellant For An Electronic Weapon Systems AndMethods For Describing Pending 11/307,572 A Deployment Unit For AnElectronic Weapon Systems And Methods For Pending 12/024,891Immobilization Using A Compliance Signal Group Systems and Methods forElectrode Pending 11/462,945 Drag Compensation Systems and Methods forCollecting Pending 11/428,881 use of Force Information Systems AndMethods For Deploying Pending 11/307,304 Electrodes For ElectronicWeaponry Systems and Methods For Arc Energy Pending 11/381,454Regulation Systems And Methods For Predicting Pending 11/285,945Remaining Battery Capacity Systems and Methods for Pending 11/307,789Immobilization Using Charge Delivery Systems and Methods For Pending11/965,638 Immobilization With Repetition Rate Control Systems AndMethods For Pending 11/965,923 Immobilization With Time MonitoringSystems And Methods Using Waveform Pending 11/566,481 Shaping Systemsand Methods for Qualified Pending 11/419,796 Registration Systems AndMethods For An Electronic Pending 11/966,511 Control Device With DateAnd Time Recording. Systems and Methods for Halting Pending 11/510,755Locomotion Systems and Methods For Halting Pending 11/966,829 LocomotionUsing Damped Waveform Systems and Methods For Pending 11/963,950Immobilization With Selected Delivered Power Projectile With SelectedDelivered Pending 11/966,728 Power Systems and Methods for PulseDelivery Pending 11/737,374 Systems And Methods For A Projectile Pending11/771,126 Having A Stabilizer For Spin Stabilization Deployment UnitFor Electronic Pending 11/696,613 Weaponry With Independent PropellantSystems And Methods For Pending 11/566,506 Immobilizing with Change ofImpedance Systems And Methods For Pending 11/769,593 ImmobilizationUsing Charge Delivered In Plural Directions . . . Systems And MethodsFor Area Pending 11/868,512 Denial Systems and Methods for DeployingPending 11/771,240 An Electrode Using Torsion Systems and Methods For ARear Pending 11/771,956 Anchored Projectile Systems And Methods ForPending 11/771,548 Unfastening A Film Of An Electrified ProjectileSystems And Methods For Arc Pending 11/943,467 Energy Regulation AndPulse Delivery

The foregoing description discusses preferred embodiments of the presentinvention, which may be changed or modified without departing from thescope of the present invention as defined in the claims. The exampleslisted in parentheses may be alternative or combined in any manner. Theinvention includes any practical combination of the structures andmethod steps disclosed. The words “and” and “or” as used herein shall beconstrued both conjunctively and disjunctively and each shall includethe other (e.g., and/or) whenever practical unless expressly statedotherwise. While for the sake of clarity of description severalspecifics embodiments of the invention have been described, the scope ofthe invention is intended to be measured by the claims as set forthbelow.

What is claimed is:
 1. A system for storing and communicating datarelated to an incident using multiple incident recorders, the systemcomprising: a first incident recorder configured to be worn by anofficer, including: a first video camera; a first pre-event buffer; afirst memory; a first user-operated control; a first rechargeablebattery; and a first short range wireless transceiver, wherein the firstincident recorder is configured to: capture first video information fromthe first video camera into the first pre-event buffer for a firstperiod of time before overwriting information previously recorded in thefirst pre-event buffer, the first information captured prior to a firstoperation of the first user-operated control; capture second videoinformation a bout the incident from the first video camera upon thefirst operation of the first user-operated control and store the secondvideo information in the first memory; record a mark in a video streamof the second video information upon a second operation of the firstuser-operated control while the second video information is beingcaptured from the first video camera, the mark indicating a time duringthe capture of the second video information at which the firstuser-operated control was operated; discontinue capture of the secondvideo information and capture third video information from the firstvideo camera in the first pre-event buffer upon third operation of thefirst user-operated control while the second video information is beingcaptured; transmit a recording support request via the first short rangewireless transceiver while at the incident; and transmit a new incidentidentifier via the first short range wireless transceiver; and a secondincident recorder configured to record the incident, including: a secondvideo camera; a second pre-event buffer; a second memory; and a secondshort range wireless transceiver, wherein the second incident recorderis configured to: capture fourth video information from the second videocamera into the second pre-event buffer for a second period of timebefore overwriting information previously recorded in the secondpre-event buffer; capture fifth video information about the incidentfrom the second video camera and store the fifth video information inthe second memory; receive the recording support request via the secondshort range wireless transceiver while at the incident; receive the newincident identifier via the second short range wireless transceiver; andassociate the new incident identifier with the incident.
 2. The systemof claim 1, wherein the recording support request includes a request torecord the incident.
 3. The system of claim 2, wherein the secondincident recorder is further configured to receive the request to recordthe incident and notify an operator of the second incident recorder ofthe request.
 4. The system of claim 1, comprising a secondary subsystemconfigured to receive the second video information from the firstincident recorder and the fifth video information from the secondincident recorder.
 5. The system of claim 4, wherein the secondarysubsystem comprises a shift hub, the shift hub including a processor anddocks configured to accept the first incident recorder and the secondincident recorder via plug-in to a wired network.
 6. The system of claim5, wherein: the second incident recorder is configured to be worn by asecond officer; the second incident recorder includes a secondrechargeable battery; and the shift hub is configured to: provide datatransfer from the first incident recorder; provide data transfer fromthe second incident recorder; recharge the first rechargeable battery ofthe first incident recorder; and recharge the second rechargeablebattery of the second incident recorder.
 7. The system of claim 6,wherein the data transfer from the first incident recorder includes thesecond video information and first usage logs from the first incidentrecorder; and the data transfer from the second incident recorderincludes the fifth video information and second usage logs from thesecond incident recorder.
 8. The system of claim 7, wherein the firstusage logs from the first incident recorder include first environmentlogs updated in response to first notice of a candidate beacon received;and the second usage logs from the second incident recorder includesecond environment logs updated in response to second notice of thecandidate beacon received.
 9. The system of claim 7, wherein the secondusage logs from the second incident recorder include second environmentlogs updated in response to a directive received for coordinatedevidence collection from the first incident recorder.
 10. The system ofclaim 9, wherein the updated second environment logs include a record ofa type of first incident recorder from which the directive was receivedand a record of what the directive required of the second incidentrecorder.
 11. The system of claim 4, wherein the first incident recorderis configured to store a first identity of an operator of the firstincident recorder; and the second incident recorder is configured tostore a second identity of an operator of the second incident recorder.12. The system of claim 11, wherein the secondary subsystem isconfigured to transmit the first identity of the operator of the firstincident recorder to the first incident recorder and transmit the secondidentity of the operator of the second incident recorder to the secondincident recorder.
 13. The system of claim 4, wherein the secondarysubsystem is configured to: receive the new incident identifier from thefirst incident recorder; receive the new incident identifier from thesecond incident recorder; and associate the second video information andthe fifth video information based on the new incident identifier. 14.The system of claim 1, comprising a primary subsystem separate from thefirst incident recorder and the second incident recorder, the primarysubsystem including a processor and a third short range wirelesstransceiver and further configured to receive the recording supportrequest from the first incident recorder via the third short rangewireless transceiver and transmit the recording support request to thesecond incident recorder via the third short range wireless transceiverto the second incident recorder.
 15. The system of claim 14, wherein theprimary subsystem is configured to: receive a second transmission fromthe first incident recorder, the second transmission comprisinginformation intended for the second incident recorder with respect tothe recording support request; and forward a copy of the informationintended for the second incident recorder with respect to the recordingsupport request to the second incident recorder, wherein the secondtransmission is received after the recording support request is receivedby a secondary subsystem.
 16. The system of claim 1, wherein the secondincident recorder is configured to transmit an acknowledgement of thenew incident identifier received from the first incident recorder. 17.The system of claim 1, wherein the first incident recorder is configuredto transmit a beacon of identification; and the second incident recorderis configured to transmit a unique address of the second incidentrecorder in response to receiving the beacon of identification from thefirst incident recorder.
 18. The system of claim 1, wherein transmittingthe new incident identifier via the first short range wirelesstransceiver includes transmitting a specified past start time prior to athird time at which the new incident identifier is transmitted by thefirst incident recorder.
 19. A computer-implemented method performed byincident recorders for storing and communicating data related to acurrent or next incident, the method comprising: capturing, by a firstincident recorder, first video information from a first video camera ofthe first incident recorder into a first pre-event buffer of the firstincident recorder for a period of time before overwriting informationpreviously recorded in the first pre-event buffer, the first videoinformation captured prior to a first operation of a user-operatedcontrol of the first incident recorder; capturing, by the first incidentrecorder, second video information about the incident from the firstvideo camera upon the first operation of the user-operated control andstore the second video information in a first memory of the incidentrecorder; recording, by the first incident recorder, a mark in a videostream of the second video information upon a second operation of theuser-operated control while the second video information is beingcaptured in the first memory, the mark indicating a time during thecapture of the second video information at which the user-operatedcontrol was operated; discontinuing, by the first incident recorder,capture of the second video information and capturing third videoinformation from the first video camera in the first pre-event bufferupon third operation of the user-operated control while the second videoinformation is being captured; receiving, by the first incidentrecorder, a recording support request from an other incident recorder atthe incident via a first short range wireless transceiver of the firstincident recorder; receiving, by the first incident recorder, a newincident identifier from the other incident recorder at the incident viathe first short range wireless transceiver; associating, by the firstincident recorder, the new incident identifier with the incident;notifying, by the first incident recorder, an operator of the firstincident recorder of the received recording support request, wherein therecording support request includes a request to record the incident andthe first incident recorder is configured to be worn by a lawenforcement officer at the incident; capturing, by the other incidentrecorder, fourth video information from a second video camera of theother incident recorder into a second pre-event buffer of the otherincident recorder for a second period of time before overwritinginformation previously recorded in the second pre-event buffer;capturing, by the other incident recorder, fifth video information aboutthe incident from the second video camera and storing the fifth videoinformation in a second memory of the other incident recorder;transmitting, by the other incident recorder, the recording supportrequest via a second short range wireless transceiver of the otherincident recorder while at the incident; and transmitting, by the otherincident recorder, the new incident identifier via the second shortrange wireless transceiver.
 20. The method of claim 19, furthercomprising: transferring, by the first incident recorder, the secondvideo information from the first incident recorder via a first dock of ashift hub; transferring, by the second incident recorder, the fifthvideo information from the second incident recorder via a second dock ofthe shift hub; recharging, by the first incident recorder, a firstrechargeable battery of the first incident recorder via the first dock;and recharging, by the second incident recorder, a second rechargeablebattery of the second incident recorder via the second dock.